[SERVER-58989] Make timestamp required in DatabaseVersionBase IDL Created: 01/Aug/21 Updated: 29/Oct/23 Resolved: 16/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 5.0-cleanup, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2021-08-09, Sharding EMEA 2021-08-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The timestamp field in DatabaseVersionBase IDL was added in 5.0. Because it previously didn't exist in 4.4, it was marked as 'optional: true', so that we can load the collections that were already present in 4.4. When upgrading to 5.0, the timestamp field will be added to the collections that didn't have it. This ensures that when upgrading to 5.1, we are guaranteed that all collections have a timestamp. This ticket is to change the timestamp field in DatabaseVersionBase to be required (optional: false), once 5.0 has branched out |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 16/Aug/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |