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

PlanStages shouldn't have to track OperationContext pointers

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Internal Code, Querying
    • Labels:
      None
    • Fully Compatible
    • Quint Iteration 7

      We discussed introducing a "PlanContext" struct to the query system similar to agg's ExpressionContext struct. This would hold all data that needs to be shared by all parts of a single query plan, including the WorkingSet and an OperationContext pointer. This would allow us to alter the OperationContext pointer in a single place during getmores rather than in each stage.

      Now just having PlanStage manage the OperationContext* in the base class rather than having the children stages manage their own.

            Assignee:
            qingyang.chen Qingyang Chen
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: