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

Negate index bounds for $not instead of defaulting to a collection scan

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.5.5
    • 2.6.0-rc0
    • Querying
    • ALL

    Description

      For a query like 

       { a: { $elemMatch: { $gt:4, $not: { $gte:6 } } } }

      the index bounds for an index on "a" should be (4, 6). When handling the $not, we should invert the bounds of its predicate to determine its bounds.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-12531 $not expression inside $elemMatch causes assertion error

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-12684 incorrect result and index not used for $ne with sparse index

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

          Task - A task that needs to be done. DOCS-2977 Doc behavior changes related to indexing negations such as $not and $ne

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              david.storch@mongodb.com David Storch
              samantha.ritter@mongodb.com Samantha Ritter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: