[SERVER-52588] Making the upgrade/downgrade process work for the Epoch to ClusterTime migration Created: 03/Nov/20 Updated: 29/Oct/23 Resolved: 03/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-0-Metadata-Format | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14 |
| Participants: |
| Description |
|
The goal of this task is to define and implement the downgrade/upgrade process that transforms database/chunk versions that work with epochs into versions that work with ClusterTime and viceversa.
On downgrade from 5.0 to 4.4, the timestamp field of DatabaseType, CollectionType and ShardCollectionType will need to be deleted. |
| Comments |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |
| Comment by Githook User [ 01/Dec/20 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |