Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.3
-
None
-
None
-
New
Description
StandardQueryNodeProcessorPipeline runs MultiFieldQueryNodeProcessor before GroupQueryNodeProcessor.
MultiFieldQueryNodeProcessor, if it encounters a node with no field, will do this:
return new GroupQueryNode(new BooleanQueryNode(children));
GroupQueryNodeProcessor comes along later on, sees that no operator is specified, so it applies the default operator, which, if set to 'AND', results in:
+properties:text +text:text
Which I don't think matches the intent of the multi-field processor.