Move management of aggregation "context" into AggregationPlan

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
              Chris Wolff
              Reporter:
              Will Buerger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: