[ http://issues.apache.org/jira/browse/LUCENE-605?page=all ]
Hoss Man resolved LUCENE-605:
-----------------------------
Resolution: Fixed
Changes have been commited.
I modified the code slightly from the most recent patch, to include a new
producted "getSummary()" method in Explanation which is used toString and
toHtml, and overridden by ComplexExplanation ... making it unneccessary to
cut/paste the toString/toHtml code from Explanation.
> 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: LUCENE-605-fix-with-subclassing.patch, demo-fix.patch,
> demo-subclassing-explanation-approach.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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
