[SERVER-71484] Don't store queries directly on the OperationContext Created: 18/Nov/22  Updated: 29/Oct/23  Resolved: 23/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Maddie Zechar
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-71143 Rewrite planning time metric to be st... Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-02-06
Participants:

 Description   

We are currently storing a copy of each query directly on the OperationContext.

This is a layering violation and we should either use a decoration or just pass the relevant variables down the stack.



 Comments   
Comment by Githook User [ 23/Jan/23 ]

Author:

{'name': 'Maddie Zechar', 'email': 'mez2113@columbia.edu', 'username': 'madelinezec'}

Message: SERVER-71484 Store telemetry key on OpDebug
Branch: master
https://github.com/mongodb/mongo/commit/2091bc8a02bc884e8df85fb02f706aac18b6278e

Comment by Githook User [ 23/Jan/23 ]

Author:

{'name': 'Maddie Zechar', 'email': 'mez2113@columbia.edu', 'username': 'madelinezec'}

Message: SERVER-71484 Store telemetry key on OpDebug
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/3694e15b00919782064ae0febbeb42b000d1a928

Comment by Maddie Zechar [ 18/Nov/22 ]

In regards to your comment louis.williams@mongodb.com please see https://jira.mongodb.org/browse/SERVER-71143

Comment by Louis Williams [ 18/Nov/22 ]

Same comment applies to the query planning information that we also store on the OpCtx

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