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

MatchExpression tree should keep track of the full path to each leaf node

    • Query Optimization

      Right now a leaf node will have the "local" path, but not the full context. For example, in both of the following queries there will be an equality node with the path "foo":

      {foo: 4}
      {a: {$elemMatch: {foo: 4}}
      

      In the second query, the full path for that equality is really "a.foo". As a result, a lot of planning logic has to manually keep track of the full path to accomodate this. For example this logic in QueryPlannerIXSelect::getFields()

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: