[
https://issues.apache.org/jira/browse/LUCENE-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879412#comment-13879412
]
Trejkaz commented on LUCENE-3355:
---------------------------------
Looks like this has been fixed at some point between 3.6.0 and 3.6.2.
> Incorrect behaviour of MultiFieldQueryNodeProcessor when default operator is
> 'AND'
> ----------------------------------------------------------------------------------
>
> Key: LUCENE-3355
> URL: https://issues.apache.org/jira/browse/LUCENE-3355
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/queryparser
> Affects Versions: 3.3
> Reporter: Trejkaz
>
> StandardQueryNodeProcessorPipeline runs MultiFieldQueryNodeProcessor before
> GroupQueryNodeProcessor.
> MultiFieldQueryNodeProcessor, if it encounters a node with no field, will do
> this:
> {code}
> return new GroupQueryNode(new BooleanQueryNode(children));
> {code}
> GroupQueryNodeProcessor comes along later on, sees that no operator is
> specified, so it applies the default operator, which, if set to 'AND',
> results in:
> {code}
> +properties:text +text:text
> {code}
> Which I don't think matches the intent of the multi-field processor.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
