[SERVER-82316] Handle direct connections for DDL commands Created: 19/Oct/23 Updated: 28/Nov/23 Resolved: 28/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | PM-3364-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-30 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Now that unsharded collections are being tracked, it is necessary to change single shard cluster's DDL operations with direct connections so they can consider the config server, this means, using the DDLCoordinator version of the command so the metadata is properly handled in the config server. |
| Comments |
| Comment by Pierlauro Sciarelli [ 28/Nov/23 ] |
|
Closing as "gone away" because |