[LUCENE-3355] Incorrect behaviour of MultiFieldQueryNodeProcessor when default operator is 'AND'

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.3
• Component/s: modules/queryparser
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Trejkaz
• Created: 02/Aug/11 05:49
• Updated: 28/Aug/22 12:54

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.