feat(oss-opensearch): Add KNN derived source configuration option #632
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.
Problem
OpenSearch 3.x+ enables
knn.derived_source.enabledby default, which allows OpenSearch to derive vectors from the vector values file instead of storing them in the_sourcefield. However, users need a way to control this behavior for their specific use cases:_sourcefor specific requirementsSolution
Added a new configurable option
knn_derived_source_enabledallowing users to:Changes
knn_derived_source_enabled: str | None = Nonefield toOSSOpenSearchIndexConfig_create_index()- only added when explicitly setCaseConfigParamTypeBenefits
Files Changed
vectordb_bench/backend/clients/oss_opensearch/config.pyvectordb_bench/models.pyvectordb_bench/backend/clients/oss_opensearch/oss_opensearch.pyvectordb_bench/frontend/config/dbCaseConfigs.pyScreenshots