[GitHub] [lucene] zacharymorn commented on issue #11915: Make Lucene smarter about long runs of matches

["zacharymorn (via GitHub)" <gi...@apache.org>]

zacharymorn commented on issue #11915:
URL: https://github.com/apache/lucene/issues/11915#issuecomment-1426607516

   This is an interesting idea @jpountz ! From my understanding of your description, this new API may need to provide these two guarantees:
   1. It returns the next doc ID that may not be a match, so the returned doc ID requires further check to confirm if it's actually a match or not (I'm guessing this from the propose default implementation of the API to return `docID() + 1` )
   2. `peekNextNonMatchingDocID() - 1` is guaranteed to not be a match. 
   
   But I'm wondering if it will be better for the API to just return the next, furthest out doc ID that we know is not going to be a match?


-- 
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-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org