[ http://issues.apache.org/jira/browse/LUCENE-451?page=comments#action_12331818 ]
paul.elschot commented on LUCENE-451: ------------------------------------- I fully agree, but IndexSearcher.java at line 107 does not conform, it will only provide a hit when its score is positive. Implementing Explanation.matched() could be more than a bit of work, because many existing explain() methods will be need to be adapted. Explanation.setMatched() would also be needed, although such a flag could be set to true by default. Regards, Paul Elschot. > BooleanQuery explain with boost==0 > ---------------------------------- > > Key: LUCENE-451 > URL: http://issues.apache.org/jira/browse/LUCENE-451 > Project: Lucene - Java > Type: Bug > Components: Search > Versions: CVS Nightly - Specify date in submission > Reporter: Yonik Seeley > Priority: Minor > > BooleanWeight.explain() uses the returned score of subweights to determine if > a clause matched. > If any required clause has boost==0, the returned score will be zero and the > explain for the entire BooleanWeight will be simply Explanation(0.0f, "match > required"). > I'm not sure what the correct fix is here. I don't think it can be done > based on score alone, since that isn't how scorers work. Perhaps we need a > new method "boolean Explain.matched()" that returns true on a match, > regardless of what the score may be? > Related to the problem above, even if no boosts are zero, it it sometimes > nice to know *why* a particular query failed to match. It would mean a > longer explanation, but maybe we should include non matching explains too? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - 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]
