You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: solutions/search/vector/knn.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -915,7 +915,7 @@ All forms of quantization will result in some accuracy loss and as the quantizat
915
915
*`int4` requires some rescoring for higher accuracy and larger recall scenarios. Generally, oversampling by 1.5x-2x recovers most of the accuracy loss.
916
916
*`bbq` requires rescoring except on exceptionally large indices or models specifically designed for quantization. We have found that between 3x-5x oversampling is generally sufficient. But for fewer dimensions or vectors that do not quantize well, higher oversampling may be required.
917
917
918
-
You can use the `rescore_vector`[preview]option to automatically perform reranking. When a rescore `oversample` parameter is specified, the approximate kNN search will:
918
+
You can use the [`rescore_vector` option](https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-search#operation-search-body-application-json-knn-rescore_vector) to automatically perform reranking. When a rescore `oversample` parameter is specified, the approximate kNN search will:
919
919
920
920
* Retrieve `num_candidates` candidates per shard.
921
921
* From these candidates, the top `k * oversample` candidates per shard will be rescored using the original vectors.
0 commit comments