You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Trejkaz (JIRA)" <ji...@apache.org> on 2011/08/02 07:50:27 UTC
[jira] [Created] (LUCENE-3355) Incorrect behaviour of
MultiFieldQueryNodeProcessor when default operator is 'AND'
Incorrect behaviour of MultiFieldQueryNodeProcessor when default operator is 'AND'
----------------------------------------------------------------------------------
Key: LUCENE-3355
URL: https://issues.apache.org/jira/browse/LUCENE-3355
Project: Lucene - Java
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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org