[SERVER-66472] Pull the epoch/timestamp parts of ChunkVersion into a CollectionGeneration class Created: 16/May/22  Updated: 29/Oct/23  Resolved: 17/May/22

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

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

Issue Links:
Gantt Dependency
has to be done before SERVER-65530 Get rid of all legacy ChunkVersion pa... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30
Participants:

 Description   

The ChunkVersion consists of a "most-significant" epoch/timestamp part which represents the generation of the collection and a subordinate major/minor parts. There are a lot of places in the code which either use epoch/timestamp separately or a half-initialised ChunkVersion in order to ensure that two collections are the same. This logic should be extracted into a separate class called CollectionGeneration instead.



 Comments   
Comment by Githook User [ 17/May/22 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-66472 Pull the collection generation out of ChunkVersion
Branch: master
https://github.com/mongodb/mongo/commit/03d8a49fd41dccdce2f2ec5bdaeb30162bee69e8

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