-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
SERVER-77112 changed the index created for the shard key {timeField: 1}. SERVER-84180 will update existing indexes from {metaField: 1} to {metaField:1, timeField:1} using the updated index definition, which is {control.min.time: 1. control.max.time:1}. However, we need to ensure that if users use shardCollection and refineCollectionShardKey with this updated definition, they can upgrade/downgrade as usual. This ticket should handle writing that test and adding changes to the FCV upgrade/downgrade process if needed. Some of the scenarios that need to be tested are:
- shardCollection with the new index definition, downgrade the FCV, call refineCollectionShardKey, then upgrade FCV again.
- shardCollection with downgraded FCV, then upgrade the FCV, confirm that queries work as expected, and then call refineCollectionShardKey.
- shardCollection with upgraded FCV, downgrade FCV, and ensure queries work as expected.
Currently, SERVER-77112 is gated by the feature flag AuthoritativeShardCollection belonging to PM-1941. This change should be made before the feature flag is enabled.
- depends on
-
SERVER-84180 refineCollectionShardKey does not rewrite the new shard key for time-series collections
- Backlog
- is related to
-
SERVER-77112 shardCollection and createIndex create different indexes on time-series buckets collections
- Closed