[SERVER-64317] Remove actualCollection from CollectionUUIDMismatch error response Created: 08/Mar/22 Updated: 17/Feb/23 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Sprint: | Execution Team 2022-08-22 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently when a CollectionUUIDMismatch error is returned, it contains the name of the collection which corresponds to the provided UUID. However for sharded clusters, the implementation of this was a bit fragile. If we're able, we should consider removing this actualCollection field so that future sharding work does not have to take these edge cases into consideration. |