benwtrent commented on PR #14167:
URL: https://github.com/apache/lucene/pull/14167#issuecomment-2616250521
@mayya-sharipova maybe a search time flag is possible, but it would stink to
have a "inconsistent but fast" flag that users then have to worry about.
I don't know of another query where multiple passes over a static dataset
can return different docs.
It seems that the default behavior should be consistency.
I think we need to do one of the following:
- fix multi-threaded consistency with information sharing (my first choice
if I had a magic wand)
- turn off direct multi-threaded queries in kNN (my second choice)
- turn off information sharing between segments (the last resort)
I would rather keep doing less work with information sharing and use less
threads than to do more work while also using more threads. However, if I can
magically have both, I prefer it.
I am curious to the opinions of others here: @jpountz @msokolov @mikemccand
Another consideration is if this is enough for a bugfix in Lucene 9.12.x.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
