[
https://issues.apache.org/jira/browse/LUCENE-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998517#comment-12998517
]
Hoss Man commented on LUCENE-2936:
----------------------------------
bq. Isn't that a bug?
bq. We fixed our search code to not discard negative scores, so explain should
also handle that?
i hav'nt read hte whole issue, but as i recall this is just a default
assumption in hte legacy base class, most use cases should be using the
"Complex" suclass where the match property can be set explicitly.
> score and explain don't match
> -----------------------------
>
> Key: LUCENE-2936
> URL: https://issues.apache.org/jira/browse/LUCENE-2936
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9.4, 3.0.3, 3.1, 4.0
> Reporter: Koji Sekiguchi
> Assignee: Robert Muir
> Priority: Minor
> Attachments: LUCENE-2936.patch, LUCENE-2936.patch, TestScore.java
>
>
> I've faced this problem recently. I'll attach a program to reproduce the
> problem soon. The program outputs the following:
> {noformat}
> ** score = 0.10003257
> ** explain
> 0.050016284 = (MATCH) product of:
> 0.15004885 = (MATCH) sum of:
> 0.15004885 = weight(f1:"note book" in 0), product of:
> 0.3911943 = queryWeight(f1:"note book"), product of:
> 0.61370564 = idf(f1: note=1 book=1)
> 0.6374299 = queryNorm
> 0.38356602 = fieldWeight(f1:"note book" in 0), product of:
> 1.0 = tf(phraseFreq=1.0)
> 0.61370564 = idf(f1: note=1 book=1)
> 0.625 = fieldNorm(field=f1, doc=0)
> 0.33333334 = coord(1/3)
> {noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
