shimpeko opened a new pull request, #15659: URL: https://github.com/apache/lucene/pull/15659
This change checks clause bulk scorers up front and only uses DisjunctionMaxBulkScorer if at least one clause is non-default. Otherwise we fall back to the scorer-based path when bulk scoring doesn't pay off. https://github.com/apache/lucene/commit/c88f9334e5c99abbeb4f233f9606873e5037c118 made DisjunctionMaxQuery use DisjunctionMaxBulkScorer when tieBreakerMultiplier == 0 and scoreMode == TOP_SCORES. That bulk scorer only helps if at least one clause provides a specialized BulkScorer. When all clauses return DefaultBulkScorer (e.g., ConstantScoreQuery), the windowing + replay path adds overhead without any bulk-scoring wins. Fixes: https://github.com/apache/lucene/issues/15658 Related PR: https://github.com/apache/lucene/pull/14040 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
