lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Updated: (LUCENE-451) BooleanQuery explain with boost==0
Date Wed, 21 Jun 2006 01:02:30 GMT
     [ ]

Hoss Man updated LUCENE-451:


a revised version of hte previous tst patch ... this fixes a lot of the things that made the
tests "invalid" before -- cheifly by:
  1) using a Similarity that doesn't choke on boosts of 0.0
  2) using a HitCollector to check matching (which is neccessary when matching docs have scores
of 0)

..also in this patch is a tweak to the way the expected results are tested -- first by looking
at the set of matching documents *then* look at the explanations for those documents (which
makes it obvious when your assumptions about what matches are wrong before you look at why
the explanation doesn't equal what it should)

> BooleanQuery explain with boost==0
> ----------------------------------
>          Key: LUCENE-451
>          URL:
>      Project: Lucene - Java
>         Type: Bug

>   Components: Search
>     Versions: CVS Nightly - Specify date in submission
>     Reporter: Yonik Seeley
>     Assignee: Hoss Man
>     Priority: Minor
>  Attachments:,
> BooleanWeight.explain() uses the returned score of subweights to determine if a clause
> 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:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message