perf: Fix OpenSearch memory problems #2019
Merged
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.
Using Lucene engine implementation for vector search because of reasons ([RFC] Lucene based kNN search support in core OpenSearch opensearch-project/OpenSearch#3545).
=> This option is only available for OpenSearch >= 2.2
Remove word cloud computation and indexing with a multilingual analyzer (reduce the indexing resources). The better way to compute this word/term cloud will be using a list of provided tokens or tokenizer instead of our custom one.