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

Non-multikey sparse indexes can be used to answer query with {$ne:null} predicate

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.4
    • Component/s: Querying
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Query 2018-10-08, Query 2018-10-22

      Description

      Sparse indexes normally can't answer inequality queries because they don't know all the unindexed documents, but the exception to that is inequality to null since it's just a subset of $exists:true predicate which sparse indexes can answer.

      This ticket is to allow sparse indexes to be used for {$ne:null} queries.

      Additionally, we will add $** testing to null_query_semantics.js

        Attachments

          Issue Links

          related to

          Task - A task that needs to be done. SERVER-36681 Change {$ne: null} semantics to be more intuitive

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-19742 Equality to null predicates can sometimes be answered using a sparse, compound index

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

            Activity

              People

              Assignee:
              ian.boros Ian Boros
              Reporter:
              asya Asya Kamsky
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: