Re: KnnQueries and result discrepancy between indexes with the same data

2024-10-02 Thread Rui Wu
Hi all, We happen to be testing on similar things. Based on our experience: 1) For one index that is not changing anymore: issuing the same queries repeatedly will generate the same results. This is true with concurrent segment search on. But we are not so sure if this still holds after https://g

Re: KnnQueries and result discrepancy between indexes with the same data

2024-09-12 Thread Marc Davenport
Adrien & Micheal. Thanks for confirming what I suspected. I think in the long run I will be ok as our users have a sticky session to an instance for some other reasons already. Marc On Thu, Sep 12, 2024 at 6:03 PM Michael Sokolov wrote: > > If your two indexes load data sequentially and in the

Re: KnnQueries and result discrepancy between indexes with the same data

2024-09-12 Thread Michael Sokolov
> If your two indexes load data sequentially and in the same order, then I believe that you would get the same results. But we consider this an implementation detail rather than a guarantee that Lucene should have. You might even still be surprised by nondeterminism arising from concurrency during

Re: KnnQueries and result discrepancy between indexes with the same data

2024-09-12 Thread Adrien Grand
Indeed, the load order can influence Lucene's approximate nearest neighbor search results. If your two indexes load data sequentially and in the same order, then I believe that you would get the same results. But we consider this an implementation detail rather than a guarantee that Lucene should