[SERVER-78307] SBE scan stage may process wildcard index reserved record id and erroneously thinks there is index corruption Created: 21/Jun/23  Updated: 29/Oct/23  Resolved: 27/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc6

Type: Bug Priority: Major - P3
Reporter: Rui Liu Assignee: Ruoxin Xu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-78274 SBE should use expanded index pattern... Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: QE 2023-06-26
Participants:

 Description   

Currently when SBE scan stage seeks a reserved record id from wildcard index (due to unbounded index scan), it may decide there's an index corruption, when it's actually harmless.



 Comments   
Comment by Githook User [ 27/Jun/23 ]

Author:

{'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}

Message: SERVER-78307 Avoid compound wildcard indexes scanning the reserved recordID

(cherry picked from commit 4246c1a133315645fa996f412cf83732a8bb8e89)
Branch: v7.0
https://github.com/mongodb/mongo/commit/e4bed2d4860fd3551bb27b252b1af6fe2957129c

Comment by Githook User [ 27/Jun/23 ]

Author:

{'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}

Message: SERVER-78307 Avoid compound wildcard indexes scanning the reserved recordID
Branch: master
https://github.com/mongodb/mongo/commit/4246c1a133315645fa996f412cf83732a8bb8e89

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