TX, Let's make it reproducible first as I can't replicate the second failure. If it's still a bug we'll create a new Jira ticket for it as this bug wasn't fixed explicitly by LUCENE-6601, rather as a side effect.
I've created a new branch on my github fork of the source code at https://github.com/shebiki/lucene-solr/commits/explain-bug-tx to show the patch and your test. It contains just one commit: https://github.com/shebiki/lucene-solr/commit/5f51944ccbd6b6622ab734e6567b24f7cb01d06c Does this work for you? If not, let me know which version of Lucene you are using and I'll rebase the patch and help narrow down the failure. --Terry On Wed, Jul 15, 2015 at 1:15 AM, Trejkaz <trej...@trypticon.org> wrote: > The Explanation is "interesting"... > > 1 = {org.apache.lucene.search.Explanation@1836} "0.0 = No match on id > 0\n" > match = true > value = 0.0 > description = {java.lang.String@1839} "No match on id 0" > details = > {java.util.Collections$UnmodifiableRandomAccessList@1840} size = 0 > > So it even says "no match" but then sets match = true, heh. > > TX > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
