lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-605) Make Explanation include information about match/non-match
Date Mon, 19 Jun 2006 18:56:30 GMT
    [ ] 

Hoss Man commented on LUCENE-605:

Hmmm... a subclass relationship might make a lot of sense here ... if we add an isMatch()
method to the existing "Explanation" which infers it's state from the value, a subclass could
allow the matchiness to be explicitly set in cases where it makes sense.  This would have
the added benefit of reducing the amount of changes needed in all of hte vaiours uses of Explanation
rihgt now.

Making a new MatchExplanation that superclasses Explanation seems trickier .. MatchExplanation
would need a setMatch method to be usefull, but we dont' want that method in Explanation (so
we'd need to override it to through an unsupported exception orosmething).  Personally I don't
think having MatchExplanation subclass Explanation would be all that confusion if a new Matcher
auperinterface was added above Scorer -- there's no direct correllary between a Scorer and
an Explanation anyway (that's what started this whole discussion right, that Explanation is
frequencly used to model things much smaller then a basic Doc/Score.

> Sorry for the rant, I should take a bit more time to consider things before typing comments..., I'm more jaded then I thought ... It didn't even occur to me that you were ranting.

> Make Explanation include information about match/non-match
> ----------------------------------------------------------
>          Key: LUCENE-605
>          URL:
>      Project: Lucene - Java
>         Type: Improvement

>   Components: Search
>     Reporter: Hoss Man
>     Assignee: Hoss Man
>  Attachments: demo-fix.patch
> As discussed, I'm looking into the possibility of improving the Explanation class to
include some basic info about the "match" status of the Explanation -- independent of the
> This is neccesary to deal with things like LUCENE-451

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