[SERVER-40843] Investigate if it is OK for opCtx to be nullptr in the TaskExecutorCursor's destructor Created: 26/Apr/19 Updated: 06/Dec/22 Resolved: 22/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Evan Nixon | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
Investigate if it is OK for opCtx to be a nullptr when used to create a RemoteCommandRequest in the TaskExecutorCursor constructor.
Further investigate if this is true in a more general scope, and if this has implications for the necessity of the doDispose method in other pipeline stages. |
| Comments |
| Comment by David Storch [ 22/May/19 ] |
|
We're not planning to do this investigation given the current schedule for the project. |