don't punt all not/nor to collscan.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.5
    • Affects Version/s: None
    • Component/s: Querying
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we just output a collscan if we see a NOT/NOR. This is too conservative. We should just not descend down a not/nor when tagging the pred tree and go through planning as usual. Enumeration should stop if it sees a negation as well. This way we'll still affix a negation as a filter if there's an and-related pred that can use an index.

        1. server11446.js
          1 kB
          Benety Goh

            Assignee:
            Benety Goh
            Reporter:
            hari.khalsa@10gen.com
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: