$or don't check already returned values in matcher for nonoverlapping index ranges

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Performance, Querying
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With $or matching, there is a step where we check that a document would not have been returned while processing previous or clauses. If an earlier or clause was handled using a disjoint range of the same index as the current clause, we can avoid performing this check.

            Assignee:
            Unassigned
            Reporter:
            Aaron Staple (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: