Nested $or queries with $text nodes should use the $or with clustered collection scan

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-77280 added queries during subplanning for $or that will allow plans with OR and clustered collection scans. SERVER-61259 extended these plans to work with $text nodes. However, subplanning is only entered for rooted $or queries, so queries like the one below won't use the new plans. We should add logic to use the new plans with these types of queries too.

      t.find({a: 0, $or: [{_id: 2}, {$text: {$search: "foo"}}]}

              Assignee:
              [DO NOT USE] Backlog - Query Integration
              Reporter:
              Gil Alon
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: