Adrien Grand created LUCENE-10469:
-------------------------------------
Summary: ConstantScoreQuery doesn't propagate its score mode
correctly
Key: LUCENE-10469
URL: https://issues.apache.org/jira/browse/LUCENE-10469
Project: Lucene - Core
Issue Type: Task
Reporter: Adrien Grand
We just noticed a performance bug on Elasticsearch that if you issue a search
request sorted by field and the query is a MatchAllDocsQuery then everything
works as expected.
But if you change the query to be a MatchAllDocsQuery within a
ConstantScoreQuery then the query suddenly visits all matching documents. This
is due to the fact that ConstantScoreQuery always passes COMPLETE_NO_SCORES to
the inner weight, and thet the MatchAllDocsQuery's optimized bulk scorer
performs a brute-force for-loop over the documents to score unless the score
mode is not exhaustive.
The fix consists of making ConstantScoreQuery propagate a non-exhaustive score
mode to the inner weight when the score mode that is passed to the
ConstantScoreQuery is not exhaustive itself.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
