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

Move management of aggregation "context" into AggregationPlan

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Query Integration

      AggregationPlan should manage ownership of the AutoGetCollectionForReadCommandMaybeLockFree, AutoStatsTracker, and MultipleCollectionAccessor used in the run_aggregate path to make lock and collection acquisition clearer along the path. With this change, we can also then avoid the passing of "initContext" and "resetContext" lambda captures as parameters throughout the file.

      This should warrant thinking of a better name than AggregationPlan to make it clear that the structure is holding important lock state.

            Assignee:
            backlog-query-integration [DO NOT USE] Backlog - Query Integration
            Reporter:
            will.buerger@mongodb.com Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: