Re: [PR] Get better cost estimate on MultiTermQuery over few terms [lucene]

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

msfroh commented on PR #13201:
URL: https://github.com/apache/lucene/pull/13201#issuecomment-2173738398

   I should check if maybe this has been superseded by https://github.com/apache/lucene/pull/13454
   
   That change seems to look at some of the term states for the first 16 terms during rewrite. Maybe that improves the cost estimate?
   
   Or maybe this change can work on the assumption that the first 16 terms are available and use that to produce a better cost estimate if those (up-to) 16 terms are exhaustive.


-- 
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