[SERVER-45406] Provide ExpressionContext in PlanStage layer Created: 07/Jan/20  Updated: 29/Oct/23  Resolved: 17/Mar/20

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

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-46921 Make tracking of timing information i... Closed
Problem/Incident
causes SERVER-46863 findAndModify hits collator mismatch ... Closed
Related
related to SERVER-44129 Consolidate unowned and owned Collato... Closed
related to SERVER-44804 Make tracking of timing information i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-01-13, Query 2020-01-27, Query 2020-02-10, Query 2020-02-24, Query 2020-03-09, Query 2020-03-23
Participants:

 Description   

This is similar to SERVER-44804. It looks like we can get a substantial performance improvement by not collecting stats/timing info in the PlanStage layer when we don't have to.



 Comments   
Comment by Ian Boros [ 17/Mar/20 ]

Forking part two of this to SERVER-46291 since otherwise this ticket would "cross" a release boundary. Re-titling this ticket to only be about ExpressionContext and closing.

Comment by David Storch [ 03/Mar/20 ]

There were enterprise changes here (not picked up by the githook because the commit message accidentally left out the SERVER ticket number): https://github.com/10gen/mongo-enterprise-modules/commit/e2e42d112fa085846b1f7905cd90b1e7e090e1ed.

Comment by Githook User [ 28/Feb/20 ]

Author:

{'username': 'puppyofkosh', 'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com'}

Message: SERVER-45406 Plumb ExpressionContext through PlanStage

This patch includes also moves ownership of the collator to the ExpressionContext.
Branch: master
https://github.com/mongodb/mongo/commit/cfa5c05fa1855fb1a04cb3a6e2eb10a7e82bf726

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