[SERVER-78755] Add an optional<bool> `unsplittable` field to `config.collection` entries Created: 07/Jul/23 Updated: 29/Oct/23 Resolved: 25/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Enrico Golfieri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-3364-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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 ( |
| Comments |
| Comment by Githook User [ 24/Jul/23 ] |
|
Author: {'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}Message: |