[jira] [Updated] (LUCENE-6042) CustomScoreQuery Explain differs from the actual score when topLevelBoost is used.
[
https://issues.apache.org/jira/browse/LUCENE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6042:
Fix Version/s: 4.10.3
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-6042) CustomScoreQuery Explain differs from the actual score when topLevelBoost is used.
[
https://issues.apache.org/jira/browse/LUCENE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6042:
Attachment: LUCENE-6042.patch
Patch with Denis' fix and a test. I moved TestExplanations to test-framework as
BaseExplanationTestCase, and made it abstract, since thats what it is, and
added simple tests for CustomScoreQuery.
Tests pass with the fix.
> 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
> 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
[jira] [Updated] (LUCENE-6042) CustomScoreQuery Explain differs from the actual score when topLevelBoost is used.
[
https://issues.apache.org/jira/browse/LUCENE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Lantsman updated LUCENE-6042:
---
Attachment: CustomScoreQuery.patch
> 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
> Attachments: CustomScoreQuery.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
