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
-
-
SERVER-100279 Upgrade FCV Constants and Tag the first new commit in master with 8.2.0-alpha
-
- Closed
-
- has to be done after
-
-
- Closed
-
- has to be done before
-
SERVER-101684 Validate that md.timeseriesBucketingParametersHaveChanged is not present in the collection catalog
-
- Needs Scheduling
-
- is related to
-
-
- Blocked
-
-
-
- Backlog
-
- related to
-
-
- Closed
-