[SERVER-71159] Include apiStrict flag into SBE plan cache key Created: 08/Nov/22  Updated: 29/Oct/23  Resolved: 13/Feb/23

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

Type: Bug 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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.3
Sprint: QO 2023-02-06, QO 2023-02-20
Participants:
Linked BF Score: 14

 Description   

This flag can cause the query to see different sets of indexes, so we need to encode a plan cache key differently when it's set.



 Comments   
Comment by Githook User [ 14/Feb/23 ]

Author:

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

Message: SERVER-71159 Include apiStrict flag into SBE plan cache key

(cherry picked from commit 1b27b42504f05c5c8502b83c4d489230eb85c048)
Branch: v6.3
https://github.com/mongodb/mongo/commit/a74810475928c34efbbb5beda556f9a902312e2c

Comment by Githook User [ 13/Feb/23 ]

Author:

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

Message: SERVER-71159 Include apiStrict flag into SBE plan cache key
Branch: master
https://github.com/mongodb/mongo/commit/1b27b42504f05c5c8502b83c4d489230eb85c048

Comment by Anton Korshunov [ 10/Feb/23 ]

david.storch@mongodb.com I created a backport request but haven't changed the fix version to "6.3 Required" as it's only for release blockers.

Comment by David Storch [ 07/Feb/23 ]

It doesn't look like I can request a 6.3 backport yet, but given that we are shipping the SBE plan cache in 6.3, I do think that this work should be backported to the 6.3 branch. Should this also be marked as "6.3 Required" anton.korshunov@mongodb.com?

Comment by David Storch [ 16/Dec/22 ]

anton.korshunov@mongodb.com do you have a status update on this ticket?

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