[
https://issues.apache.org/jira/browse/LUCENE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996491#comment-14996491
]
Adrien Grand commented on LUCENE-6679:
--------------------------------------
5.x and trunk are indeed different, mainly because of backward compatibility
for FilteredQuery (which is gone in trunk but still exists in 5.x): since
FilteredQuery has an option that lets control whether the filter should be
executed before or after the query, Filter had to diverge a bit from trunk so
that this would remain possible (while in trunk all decisions are made
automatically now).
Terry, please let us know if you need help fixing the tests that fail with your
patch. I'd be happy to help.
> Filter's Weight.explain returns an explanation with isMatch==true even on
> documents that don't match
> ----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-6679
> URL: https://issues.apache.org/jira/browse/LUCENE-6679
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Attachments: LUCENE-6679.patch
>
>
> This was reported by Trejkaz on the java-user list:
> http://search-lucene.com/m/l6pAi19h4Y3DclgB1&subj=Re+What+on+earth+is+FilteredQuery+explain+doing+
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
