[SERVER-61240] Ensure we properly report a plan cache key if the query is eligible for SBE Created: 04/Nov/21  Updated: 29/Oct/23  Resolved: 04/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0-rc3

Type: Task Priority: Major - P3
Reporter: Anton Korshunov Assignee: Anton Korshunov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QO 2021-12-13, QO 2021-12-27, QO 2022-01-10, QO 2022-02-21, QO 2022-03-07
Participants:

 Description   

Currently we're reporting the hash of the classic plan cache key even if the query is eligible for SBE and is going to end up in the SBE cache. For example. There might be other places in the code.



 Comments   
Comment by Githook User [ 04/Mar/22 ]

Author:

{'name': 'Anton Korshunov', 'email': 'anton.korshunov@mongodb.com', 'username': 'antkorsh'}

Message: SERVER-61240 Ensure we properly report a plan cache key if the query is eligible for SBE
Branch: master
https://github.com/mongodb/mongo/commit/ee5dacd18fd01e61b449066e2081515da79a8d66

Comment by Anton Korshunov [ 31/Jan/22 ]

We should also add a few tests to validate the plan cache key is reported correctly in explain and $planCacheStats.

Comment by David Storch [ 05/Nov/21 ]

We should make sure to explicitly test this behavior for explain, system.profile, and the slow query log. And maybe $currentOp if the hash shows up there?

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