[ http://issues.apache.org/jira/browse/LUCENE-605?page=comments#action_12416788 ]
paul.elschot commented on LUCENE-605: ------------------------------------- The purpose of Explanation is to explain all the "mysteries" of query search, so it would be worthwhile to use an extra class for the micro explanations. Since these currently are just Explanations without a match, why not make the micro explanations a superclass of Explanation? It might even be simpler to make MatchExplanation a subclass of the existing Explanation, and hope that that does not break backwards compatbility later (I don't know.) Such a class structure would be counterintuitive to Matcher as superclass/superinterface of Scorer, so maybe it should be the other way round: make MatchExplanation a superclass of Explanation. Sorry for the rant, I should take a bit more time to consider things before typing comments... > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
