[SERVER-52847] Make timestamp required in CollectionType and ShardCollectionType IDL Created: 13/Nov/20  Updated: 29/Oct/23  Resolved: 21/Sep/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: Jordi Serra Torrens Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: 5.0-cleanup, neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-59770 Use the timestamp to implement the co... Closed
Gantt Dependency
has to be done after SERVER-58989 Make timestamp required in DatabaseVe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-09-20, Sharding EMEA 2021-10-04
Participants:

 Description   

The timestamp field in CollectionType and ShardCollectionType IDL was added in 5.0 (SERVER-52768). 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 CollectionType and ShardCollectionType IDL 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 [ 21/Sep/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-52847 Make timestamp required in CollectionType and ShardCollectionType IDL
Branch: master
https://github.com/mongodb/mongo/commit/9e1d37df7bf5bb4c8312f155bd671214f75ea296

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