[SERVER-79178] Make necessary routing table changes to consider the splittable field Created: 21/Jul/23  Updated: 29/Oct/23  Resolved: 27/Jul/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-3364-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-78755 Add an optional<bool> `unsplittable` ... Closed
is depended on by SERVER-79312 Make CollectionRoutingInfoTargeter ab... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-08-07
Participants:

 Description   

Currently the routing table have the isSharded verification, but after the changes of SERVER-78755 we need to also consider if there is a routing table present in order to properly route commands to appropriate shard. We could do something similar to this POC, rename the function to consider whether there is a routing table present or not.

Eventually all collections will have a proper routing table, but for now, this is an intermediary step necessary to check and modify all dependent code.



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

Author:

{'name': 'Tommaso Tocci', 'email': '58224719+toto-dev@users.noreply.github.com', 'username': 'toto-dev'}

Message: SERVER-79178 Make necessary routing table changes to consider the splittable field
Branch: master
https://github.com/mongodb/mongo/commit/cff791b689b5012ebd3e9d50128d2f23f3187d73

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