-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
2
Due to the reasons pointed out in SERVER-91194, there may be existing mongodb instances with timeseriesBucketingParametersHaveChanged set to inconsistent values.
Purpose of this ticket is to unset all existing timeseriesBucketingParametersHaveChanged options (set to boost::none) during server start up or upon setFeatureCompatibilityVersion.
- related to
-
SERVER-91194 timeseriesBucketsMayHaveMixedSchemaData not properly cloned upon data migration/initial sync/restore
- Closed