[SERVER-19364] PlanStages shouldn't have to track OperationContext pointers Created: 10/Jul/15  Updated: 19/Sep/15  Resolved: 04/Aug/15

Status: Closed
Project: Core Server
Component/s: Internal Code, Querying
Affects Version/s: None
Fix Version/s: 3.1.7

Type: Task Priority: Major - P3
Reporter: Mathias Stearn Assignee: Qingyang Chen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 7
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 04/Aug/15 ]

Author:

{u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}

Message: SERVER-19364 move query stage OperationContext pointer management into the base class
Branch: master
https://github.com/mongodb/mongo/commit/be8a683771004a2541c730a1ac0e35cd13e03a8b

Comment by Qingyang Chen [ 24/Jul/15 ]

Note*: Should have WorkingSet be a member and change everywhere where WorkingSet is constructed to construct a PlanContext instead.

Generated at Thu Feb 08 03:50:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.