-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elasticsearch 7.* and 8.* integration. OpenSearch integration. #469
Open
ivanmrsulja
wants to merge
17
commits into
vivo-project:main
Choose a base branch
from
ivanmrsulja:feature/elasticsearch-integration
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Elasticsearch 7.* and 8.* integration. OpenSearch integration. #469
ivanmrsulja
wants to merge
17
commits into
vivo-project:main
from
ivanmrsulja:feature/elasticsearch-integration
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…entation and configuration mechanisms.
ivanmrsulja
changed the title
Small mapping update and response parsing fix.
Elasticsearch 7.* and 8.* integration.
Jun 24, 2024
…-side service detection mechanism.
ivanmrsulja
changed the title
Elasticsearch 7.* and 8.* integration.
Elasticsearch 7.* and 8.* integration. OpenSearch integration.
Jul 5, 2024
The following features should be tested:
|
@ivanmrsulja please create a VIVO PR with updated example.runtime.properties. Also, please move JSON configuration into vivo-es project. Add in the vivo-es project a Docker file, and update README file to explain how ES should be run. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: