Skip to content

Conversation

@mayya-sharipova
Copy link
Contributor

Backports the following commits to 8.x:

Although scrolling is not recommended for knn queries, it is effective.
But I found a bug that when use scroll in the knn query, the But I found
a bug that when using scroll in knn query, knn_score_doc will be lost in
query phase, which means knn query does not work. In addition, the
operations for directly querying the node where the shard is located and
querying the node with transport are different. It can be reproduced on
the local node. Because the query phase uses the previous
ShardSearchRequest object stored before the dfs phase. But when it run
in the local node, it don't do the encode and decode processso the
operation is correct. I wrote an IT to reproduce it and fixed it by
adding the new source to the LegacyReaderContext.
@mayya-sharipova mayya-sharipova added :Search Relevance/Vectors Vector search >bug auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Apr 20, 2025
@elasticsearchmachine elasticsearchmachine merged commit 0aee82c into elastic:8.x Apr 20, 2025
15 checks passed
@mayya-sharipova mayya-sharipova deleted the backport/8.x/pr-126035 branch April 20, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >bug external-contributor Pull request authored by a developer outside the Elasticsearch team :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v8.19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants