[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:
Depends
is depended on by SERVER-78756 Filter out `unsplittable` field on ba... Closed
is depended on by SERVER-78763 Allow create collection coordinator r... Closed
is depended on by SERVER-78765 RoutingTableConsistencyChecker and Ch... Closed
is depended on by SERVER-79157 Change create collection coordinator ... Closed
is depended on by SERVER-79160 Track unsharded collections when addi... Closed
is depended on by SERVER-79178 Make necessary routing table changes ... Closed
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 (SERVER-75302 - that removed some fields from those components - can serve as an example to understand where to plug the new field).



 Comments   
Comment by Githook User [ 24/Jul/23 ]

Author:

{'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-78755 Add an optional<bool> unsplittable field to config.collection entries
Branch: master
https://github.com/mongodb/mongo/commit/348ebc6b8823c8bdec2a362a03ad2bb67d8fa60e

Generated at Thu Feb 08 06:39:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.