Elasticsearch 7.* and 8.* integration. OpenSearch integration. #469
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do?
Updates current ES 6.x integration to 8.x.
What's new?
Changes in ResponseParser and ES documentation on the first draft.
Example:
src/main/java/edu/cornell/mannlib/vitro/webapp/searchengine/elasticsearch/ResponseParser.java
to be in line with current ES APIsrc/main/java/edu/cornell/mannlib/vitro/webapp/searchengine/elasticsearch/Elasticsearch_notes_on_the_first_draft.md
with new mappingHow should this be tested?
Initial setup
{vitro_home}/config/applicationSetup.n3
to use this driver (see below).vitro.local.searchengine.url
configuration property to contain ES index base URL (due to backward compatibility, Solr can also be configured usingvitro.local.solr.url
. This will however result in a warning that is shown in logs, advising the client to switch to a new configuration parameter)vitro.local.searchengine.username
configuration property to contain ES/OS basic auth usernamevitro.local.searchengine.password
configuration property to contain to contain ES/OS basic auth passwordA mapping for the search index
Modify
applicationSetup.n3
Your setup should be completed now 😃 ! After this, you should perform common manual tests that are done for every new release.
Interested parties
@chenejac
Reviewers' expertise
Candidates for reviewing this PR should have some of the following expertises: