-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
Cluster Scalability 2024-4-1, Cluster Scalability 2024-4-15
SERVER-77112 and SERVER-84180 are both bugs where the index backing the shard key is not correctly rewritten for time-series buckets collection. To fix this we rewrite the index backing the shard key to use buckets collection fields. However, to fit with existing behavior validateShardKeyIndexExistsOrCreateIfPossible expects the shard key to already go through a partial rewrite and we must pass time-series options into this function call. Before calling validateShardKeyIndexExistsOrCreateIfPossible the shard key must have these two changes:
- the timeField must be rewritten to "control.min.time".
- the metaField should be rewritten to use "meta".
This ticket is ensuring the rewrite takes place and thus the correct index backing the shard key is created during reshardCollection.
- is related to
-
SERVER-84180 refineCollectionShardKey does not rewrite the new shard key for time-series collections
- Backlog
-
SERVER-77112 shardCollection and createIndex create different indexes on time-series buckets collections
- Closed
- related to
-
SERVER-89117 Complete TODO listed in SERVER-84741
- Closed