[ 
https://issues.apache.org/jira/browse/LUCENE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127002#comment-17127002
 ] 

ASF subversion and git services commented on LUCENE-9393:
---------------------------------------------------------

Commit c27b3889ae6369c4bf9ecf0ca1813051753d882b in lucene-solr's branch 
refs/heads/branch_8x from Tomas Eduardo Fernandez Lobbe
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c27b388 ]

LUCENE-9393: FunctionScoreQuery turns TOP_DOCS to COMPLETE in inner weights 
(#1553)

FunctionScoreQuery can't really use WAND algorithm even if TOP_DOCS score mode 
is requested. This commit makes the inner weight created use COMPLETE

> FunctionScoreQuery shouldn’t use TOP_DOCS for creating inner weight
> -------------------------------------------------------------------
>
>                 Key: LUCENE-9393
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9393
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Tomas Eduardo Fernandez Lobbe
>            Assignee: Tomas Eduardo Fernandez Lobbe
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> {{FunctionScoreQuery.createWeight}} creates the weight of the inner query 
> using the {{scoreMode}} from it’s input parameter, however, 
> FunctionScoreQuery can’t really use WAND algorithm, and the Scorer used will 
> ignore calls to set competitive scores.  FunctionScoreQuery should just turn 
> {{TOP_DOCS}} to {{COMPLETE}} before creating the inner query's weight.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to