[SERVER-68265] Add namespace to catalogId mapping in CollectionCatalog Created: 25/Jul/22  Updated: 29/Oct/23  Resolved: 26/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin 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-43076 What is the correct way to access the... Closed
Duplicate
duplicates SERVER-68266 Handle replication rollback in Collec... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-09-05, Execution Team 2022-09-19, Execution Team 2022-10-03
Participants:

 Description   

The CollectionCatalog need a mapping per namespace how catalogId changes over time. Given a namespace and timestamp we need to know what catalogId to use to find the corresponding durable catalog entry.

Create, drop and rename operations can change the catalogId. Cleanup may occur for times earlier than the oldest timestamp.



 Comments   
Comment by Githook User [ 26/Sep/22 ]

Author:

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

Message: SERVER-68265 Maintain historic catalogId mapping in CollectionCatalog

Mapping of namespace to catalogId is maintained for timestamps back to the oldest timestamp.
Used to be able to resolve catalogId for a namespace that is resilient to create, drop and rename operations.
Branch: master
https://github.com/mongodb/mongo/commit/62dae95dc6c02786dce1c6c97bae488ac95b9601

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