[SERVER-75818] Fix time-series options when sharding a collection Created: 07/Apr/23  Updated: 16/Jan/24  Resolved: 23/Jun/23

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

Type: Bug Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Yuhong Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-75819 Do not use default value for missing ... Blocked
Problem/Incident
causes SERVER-83114 Default timeseries options may lead t... Closed
Related
related to SERVER-85251 Remove unnecessary timeseries validat... Backlog
is related to SERVER-76242 Write a customized IDL parser for tim... Backlog
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-05-01, Execution Team 2023-05-15, Execution Team 2023-05-29, Execution Team 2023-06-12, Execution NAMR Team 2023-06-26, Execution NAMR Team 2023-07-10
Participants:
Linked BF Score: 5

 Description   

We validate and automatically fix/set the time-series options when creating the collection. When sharding a collection, we can also pass a timeseries option. If the collection already exists, we will compare the shard command time-series options and the already fixed time-series options in the catalog. This will lead to a mismatch.



 Comments   
Comment by Githook User [ 23/Jun/23 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}

Message: SERVER-75818 Validate and set time-series options when sharding a collection
Branch: master
https://github.com/mongodb/mongo/commit/cf9274031e9cb6346104f49bb24abe0097f93973

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