[ https://issues.apache.org/jira/browse/LUCENE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-6042. --------------------------------- Resolution: Fixed Fix Version/s: Trunk 5.0 Thanks Denis! > 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 > Priority: Minor > Fix For: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org