Lucene - Core
  1. Lucene - Core
  2. LUCENE-3355

Incorrect behaviour of MultiFieldQueryNodeProcessor when default operator is 'AND'

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.3
    • Fix Version/s: None
    • Component/s: modules/queryparser
    • Labels:
      None
    • Lucene Fields:
      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Trejkaz
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development