[SERVER-80389] Create specific error codes for moveCollection/unshardCollection Created: 24/Aug/23 Updated: 05/Oct/23 Resolved: 05/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Sprint: | Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16 |
| Participants: |
| Description |
|
Right now, these two commands are using the reshardCollection error codes since that is the underlying command being used. However, to avoid user confusion, create error codes specific to moveCollection/unshardCollection. We can use provenance field to distinguish between the commands and propagate the right code. |
| Comments |
| Comment by Kshitij Gupta [ 05/Oct/23 ] |
|
Users are expected to know that we will use resharding internally. So not doing this. |