[SERVER-71817] openCollection should store const instance in uncommitted catalog updates Created: 02/Dec/22  Updated: 29/Oct/23  Resolved: 17/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Will Buerger Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-68271 Trigger Collection instantiation when... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-01-09, Execution Team 2023-01-23
Participants:

 Description   

UncommittedCatalogUpdates is normally used for writable collection instances but was re-used for openCollection. This currently requires us to use a non-const Collection instance which makes it difficult to re-use current interfaces for reads that are const.



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

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71817 Store opened collections in separate data structure

Allows UncommittedCatalogUpdates to only contain actual changes and we get rid of const issues
Branch: master
https://github.com/mongodb/mongo/commit/31ee375d0956894889f39426ca56d9add25d0acb

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