Skip to content

Commit 0483056

Browse files
authored
Make rescore_vector generally available (#995)
rescore vector is GA in 9.1.
1 parent 2ad7177 commit 0483056

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

solutions/search/vector/knn.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -915,7 +915,7 @@ All forms of quantization will result in some accuracy loss and as the quantizat
915915
* `int4` requires some rescoring for higher accuracy and larger recall scenarios. Generally, oversampling by 1.5x-2x recovers most of the accuracy loss.
916916
* `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.
917917

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:
919919

920920
* Retrieve `num_candidates` candidates per shard.
921921
* From these candidates, the top `k * oversample` candidates per shard will be rescored using the original vectors.

0 commit comments

Comments
 (0)