[jira] [Resolved] (LUCENE-10469) ConstantScoreQuery doesn't propagate its score mode correctly

["Adrien Grand (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand resolved LUCENE-10469.
-----------------------------------
    Fix Version/s: 9.1
       Resolution: Fixed

> 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
>            Priority: Minor
>             Fix For: 9.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org