Can we re-enable strict checking for KNN queries?
See original GitHub issueA while back we discovered that KNN was producing non-deterministic results even on a deterministic index, and disabled strict top N hit checking for KNNVectorQuery
.
We think/thought this was because the “deterministically random” source was seeded from each segment’s GUID, but we’ve since fixed this query to use a fixed random seed (42
of course).
Can we now re-enable strict checking of the top KNN hits?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
K-Nearest-Neighbors in 6 steps. With scikit-learn in python
This aims to be an applied guide to utilizing the K-Nearest-Neighbors (KNN) method for solving business problems in python. The most popular use-case...
Read more >k-nearest neighbor (kNN) search | Elasticsearch Guide [master]
A k-nearest neighbor (kNN) search finds the k nearest vectors to a query vector ... However, you can improve latency by using a...
Read more >K-Nearest Neighbors (KNN) Algorithm for Machine Learning
The k-nearest neighbors (kNN) algorithm is a simple tool that can be used for a number of real-world problems in finance, healthcare, ...
Read more >Processing Moving kNN Queries Using Influential Neighbor Sets
In this paper, we propose a novel approach that validates kNN sets as strict as the order-k Voronoi cells, but do not have...
Read more >k-NN Painless extensions - OpenSearch documentation
With the k-NN plugin's Painless Scripting extensions, you can use k-NN ... Painless has a strict list of allowed functions and classes per...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s OK for the KNN results to change – that’s just needs a nightly regolding as long as we know/accept the source/reason for the change.
there’s also no harm in tracking relevance, if its not difficult to do. I just think we should stay “strict”