[SERVER-43207] Fix pipeline updates to use a real MongoProcessInterface rather than a Stub Created: 06/Sep/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jacob Evans Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:

 Description   

Pipeline updates use StubMongoProcessInterface currently, which happens to be ok since there are no stages that are legal in a pipeline-style update and use the mongo process interface. This sort of implicit invariant is not obvious and prone to breakage as we add new expressions/stages.



 Comments   
Comment by Nicholas Zolnierz [ 18/Oct/19 ]

I've pulled this out of the MR in Agg epic and flagged for rescheduling. We don't strictly need to do this anymore since the JS execution lives on the opCtx instead of the mongo process interface, but still seems like a worthwhile improvement to make.

Generated at Thu Feb 08 05:02:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.