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

allow $expr with $in expression use a non-multikey index

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • 3.6.0
    • None
    • Aggregation Framework
    • Query Optimization

    Description

      Similarly to SERVER-31760 it's possible to rewrite $expr with $in expression to an indexable MatchExpression.

      Semantically 

       {$expr:{$in:[ "value", [ "v1", "v2", "v3" ]] } }

      is exactly equivalent to 

       {"value":{$in:[ "v1", "v2", "v3"]}}

      if value is not an array.

      If we restrict using an index for $expr $in expressions to non-multikey indexes/paths, then we will only get back matches from the index that are guaranteed to be correct semantically to the aggregation meaning of $in.

      This is also exactly equivalent query that can use any index and return only agg semantics:

      db.reviews.find({product_id:{$in:["hat","shirt"],$not:{$elemMatch:{$exists:true}}}})

      The second part prevents reaching into arrays for comparison.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36254 No index support for filtering on array fields inside $expr operator

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36994 $expr does not use index for $in

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-38138 $expr doesn't use indexes

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-37470 Lookup sub-pipeline is not using index with the $in operator

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

          Question - SERVER-45326 Poor Aggregation Framework performance in relational queries

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

          Activity

            People

              backlog-query-optimization Backlog - Query Optimization
              asya.kamsky@mongodb.com Asya Kamsky
              Votes:
              24 Vote for this issue
              Watchers:
              39 Start watching this issue

              Dates

                Created:
                Updated: