-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
`fixed_bucketing_fcv_tolerant.js`, like other timeseries DDL tests (`bucket_granularity.js` and `bucket_timestamp_rounding.js`) seem to be   incompatible with the `disagg_repl_jscore_passthrough_multiversion` suite.
 So the `disagg_repl_jscore_passthrough_multiversion` tag was added to the test to disable the suite for now.
The goal of this task is too root-cause the issue and remove the tag.
- is related to
-
SERVER-128054 Fix stack-use-after-scope in UpdateTimeseriesBucketingParamsDisablesFixedBucketing test
-
- Closed
-
-
SERVER-129872 [TEST ONLY] Fix `list_collections_create_roundtrip.js` in FCV upgrade/downgrade suites
-
- Closed
-
-
SERVER-126821 Allow changing fixedBucketing via collMod
-
- Closed
-
-
SERVER-126822 Strip fixedBucketing field on downgrade from FCV 9.0
-
- Closed
-
-
SERVER-126823 Set fixedBucketing to true by default on newly created timeseries collections
-
- Closed
-
-
SERVER-126824 Remove legacy timeseriesBucketingParametersHaveChanged field from Global Catalog
-
- Closed
-
-
SERVER-126825 Delete/replace timeseriesBucketingParametersHaveChanged usages
-
- Closed
-
-
SERVER-126826 Enable the feature flag backing fixedBucketing at catalog level
-
- Closed
-
-
SERVER-128095 Set fixedBucketing to false on upgrade to FCV 9.0
-
- Closed
-
-
SERVER-128556 Use 'fixedBucketing' as flag for query optimization logic
-
- Closed
-
-
SERVER-130200 Add disagg_repl_jscore_passthrough_multiversion tag to fixed_bucketing_fcv_tolerant.js
-
- Closed
-
-
SERVER-128739 Add noPassthrough coverage for fixedBucketing DDL operations during FCV transitions
-
- Closed
-
-
SERVER-128741 Move timeseries_sharded_fixed_bucketing.js to jstests/core_sharding/
-
- Closed
-
-
SERVER-128767 Add fixedBucketing assertions in $out tests for stable FCV suites
-
- Closed
-