Skip to content

[KNN] Adding default value for oversampling in 9.1.0 #1290

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update documentation wording and adding version
  • Loading branch information
Samiul-TheSoccerFan committed May 5, 2025
commit 85feae8731e81e47b5ddab252e9950846e2ce7f1
2 changes: 1 addition & 1 deletion solutions/search/vector/knn.md
Original file line number Diff line number Diff line change
Expand Up @@ -901,7 +901,7 @@ Approximate kNN search always uses the [`dfs_query_then_fetch`](https://www.elas

When using [quantized vectors](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for kNN search, you can optionally rescore results to balance performance and accuracy, by doing:

* **Oversampling**: Retrieve more candidates per shard. The default is `3.0` in `bbq`.
* **Oversampling**: Retrieve more candidates per shard. Starting in `9.1.0`, the default oversampling factor is 3, but only for the `bbq` quantization method. Other quantization methods must explicitly specify an oversample value either in the field mapping or at query time.
* **Rescoring**: Use the original vector values for re-calculating the score on the oversampled candidates.

As the non-quantized, original vectors are used to calculate the final score on the top results, rescoring combines:
Expand Down
Loading