-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07
This change is needed to be able to differentiate between unsharded and sharded collections: since they will both be registered on the sharding catalog, the new field (to be added here) will be set to true when needing to represent unsharded collections that are technically not allowed to be split.
Additionally to adding the new field, adapt the ChunkManager and the ShardCollectionType in order to take into account the new parameter (SERVER-75302 - that removed some fields from those components - can serve as an example to understand where to plug the new field).
- is depended on by
-
SERVER-78756 Filter out `unsplittable` field on balancer paths
- Closed
-
SERVER-78763 Allow create collection coordinator registering unsplitable collections
- Closed
-
SERVER-78765 RoutingTableConsistencyChecker and CheckMetadataConsistency must account for tracked unsharded collections
- Closed
-
SERVER-79157 Change create collection coordinator to allow sharding unsplittable collections
- Closed
-
SERVER-79160 Track unsharded collections when adding a shard
- Closed
-
SERVER-79178 Make necessary routing table changes to consider the splittable field
- Closed