[jira] [Commented] (LUCENE-4935) CustomScoreQuery has broken boosting

["Steve Rowe (JIRA)" <ji...@apache.org>]

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

Steve Rowe commented on LUCENE-4935:
------------------------------------

If there are no objections, I'd like to backport this to 4.3.1.
                
> CustomScoreQuery has broken boosting
> ------------------------------------
>
>                 Key: LUCENE-4935
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4935
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/query/scoring
>            Reporter: Robert Muir
>             Fix For: 5.0, 4.4
>
>         Attachments: LUCENE-4935.patch, LUCENE-4935.patch
>
>
> CustomScoreQuery wrongly applies boost^2 instead of boost.
> It wrongly incorporates its boost into the normalization factor passed down to subquery (like booleanquery does) and *also* multiplies it directly in its scorer.
> The only reason the test passes today is because it compares raw score magnitudes when querynorm is on, which normalizes this away.
> Changing the test to use newSearcher() demonstrates the brokenness.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org