-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2026-03-30
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Most of the timeseries options in the local catalog are stored inside the TimeseriesOptions object that is under the CollectionOptions .
There are only 2 timeseries options that does not follow this pattern:
- timeseriesBucketsMayHaveMixedSchemaData
- timeseriesBucketingParametersHaveChanged
These options are instead stored directly in the collection metadata struct.
These 2 options have been added outside of the CollectionOptions for backward comapatibiity reason. In fact, the CollectionOptions are read with strict parsing, and we needed to introduce those options in a minor release.
The goal of this ticket is to take advantage of the next FCV upgrade procedure to bring these 2 options inside the TimeseriesOptions together with the others.
- is depended on by
-
SERVER-96831 Get rid of md.timeseriesBucketsMayHaveMixedSchemaData for avoiding confusion/misuses
-
- Blocked
-
-
SERVER-106710 Disallow setting the timeseries flags when creating a collection
-
- Blocked
-