[SERVER-78316] Sharded DDLs over unsharded collections/views shouldn't target all shards Created: 22/Jun/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, sharding-product-sync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Catalog and Routing
|
||||
| Participants: | |||||
| Linked BF Score: | 105 | ||||
| Description |
|
This behavior was introduced in 5.0 due to the fact that DDL implementations on 4.4 and prior versions might leave garbage if the operation doesn't succeed. However, this is pretty bad for unsharded collections / views: they only live on the primary shard, however we end up targeting all shards. |