-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-03-03, CAR Team 2025-03-17
-
1
Due to the reasons pointed out in SERVER-91193, 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.
- depends on
-
SERVER-91193 timeseriesBucketingParametersHaveChanged not properly cloned upon data migration/initial sync/restore
-
- Closed
-
-
-
- Blocked
-
- has to be done after
-
-
- Closed
-
- has to be done before
-
SERVER-101684 Validate that md.timeseriesBucketingParametersHaveChanged is not present in the collection catalog
-
- Backlog
-
- is related to
-
-
- Blocked
-
-
-
- Backlog
-