[DEV-11931] Implement OpenSearch client over ElasticSearch#4669
Open
DavidMikolaKC wants to merge 11 commits into
Open
[DEV-11931] Implement OpenSearch client over ElasticSearch#4669DavidMikolaKC wants to merge 11 commits into
DavidMikolaKC wants to merge 11 commits into
Conversation
…pending-api into mod/dev-11931-elasticsearch-to-opensearch
This file contains hidden or 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
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.
Description:
The USAspending API still uses Elasticsearch hosted by AWS. AWS made the switch to their own implementation known as OpenSearch and no longer updates Elasticsearch leaving the latest available version at 7.1. In aiming to use packages that officially support our current Python version we should make the switch to OpenSearch client and DSL.
Technical Details:
All imports of Elasticsearch have been replaced with the equivalent imports from the opensearch-py library
Requirements for PR Merge:
All functionalities are retained from how they operated in Elasticsearch
Explain N/A in above checklist: