gsmiller opened a new issue, #11740: URL: https://github.com/apache/lucene/issues/11740
### Description To minimize the up-front cost of creating a `ScoreSupplier`, `TermInSetQuery` doesn't actually intersect its terms with the index, which means it has no visibility into the postings length of each term for the purpose of cost estimation. Because of this, we might grossly over-estimate the cost. I wonder if we can do better somehow? As one thought, I wonder if there are any cases where it's actually justified to intersect the terms up-front? While there's a cost of doing so, having a more accurate cost estimate for the `Scorer` might be useful in some cases? -- 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.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
