[
https://issues.apache.org/jira/browse/LUCENE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235781#comment-14235781
]
ASF subversion and git services commented on LUCENE-6042:
---------------------------------------------------------
Commit 1643372 from [email protected] in branch 'dev/branches/lucene_solr_4_10'
[ https://svn.apache.org/r1643372 ]
LUCENE-6042: 4x only test tweak: supress 3x codec for all tests that subclass
this one -- needs docvals
> CustomScoreQuery Explain differs from the actual score when topLevelBoost is
> used.
> ----------------------------------------------------------------------------------
>
> Key: LUCENE-6042
> URL: https://issues.apache.org/jira/browse/LUCENE-6042
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/query/scoring
> Affects Versions: 4.8
> Reporter: Denis Lantsman
> Assignee: Robert Muir
> Priority: Minor
> Fix For: 4.10.3, 5.0, Trunk
>
> Attachments: CustomScoreQuery.patch, LUCENE-6042.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> CustomScoreQuery.java, doExplain has the following line:
> {code}
> res.addDetail(new Explanation(getBoost(), "queryBoost"));
> {code}
> This multiplies the custom score query by just the boost of the current
> query, and not by
> {code}
> queryWeight=topLevelBoost*getBoost();
> {code}
> which is the value that's actually used during scoring. This leads to
> drastically different scores in the debug info, relative to the actual score,
> when the query is a subquery of another one, like a BooleanQuery clause, with
> a non-1 boost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
