Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-11446

don't punt all not/nor to collscan.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 2.5.5
    • Querying
    • Fully Compatible
    • ALL

    Description

      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.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-10005 $exists:false prevents use of a sparse index on a different field

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-10608 {$exists: false} will not use index

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-11821 Indexes are ignored with use of $not in 2.5, obeyed in 2.4

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-11839 index is not used to provide sort for $not query

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: