-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-01-06, CAR Team 2025-01-20, CAR Team 2025-02-03, CAR Team 2025-02-17, CAR Team 2025-03-03, CAR Team 2025-03-17, CAR Team 2025-03-31, CAR Team 2025-04-14, CAR Team 2025-04-28
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Due to the reasons pointed out in SERVER-91194, there may be existing mongodb instances with timeseriesBucketsMayHaveMixedSchemaData set to inconsistent values.
Purpose of this ticket is to unset all existing timeseriesBucketsMayHaveMixedSchemaData 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
-