lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-605) Make Explanation include information about match/non-match
Date Mon, 19 Jun 2006 07:24:30 GMT
    [ http://issues.apache.org/jira/browse/LUCENE-605?page=comments#action_12416719 ] 

Hoss Man commented on LUCENE-605:
---------------------------------

> The point is that adding by adding a match indicator to Explanation, Explanation becomes
less useful
> to explain a subformula of a (matching) score value, in this case the coordination factor.

yeah ... when I added "getMatchString()" to the toString() value It hit me that eliminating
that other constructor (or more specificly: eliminating Explanations without a "match" state)
is really impractical.  Many of the "micro explanations" of things like coord value and tf,
and idf don't really make sense with a "match" boolean, and even the ones that do don't really
need it.   But if anything that just reaffirmed my faith in the isMatch() function using the
Boolean if it's set, and infering it from the float value if it's not -- but eliminating the
2 arg constructor is certainly impractical -- so is automatically including the getMatchString()
in the toString(int) .. but I am thinking that if/when I change all the Query.explain methods
to use the new match Boolean, I'll also update the description to say wether it was a match
.. either that or add it to the toString() method (ie: just at the top level without the recursion)
... but that's a secondary isue to getting the logic right.


> Make Explanation include information about match/non-match
> ----------------------------------------------------------
>
>          Key: LUCENE-605
>          URL: http://issues.apache.org/jira/browse/LUCENE-605
>      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
value...
> http://www.nabble.com/BooleanWeight.normalize%28float%29-doesn%27t-normalize-prohibited-clauses--t1596471.html#a4347644
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message