[SERVER-46654] Munge Egress Responses into a ErrorExtraInfo subclass Created: 05/Mar/20 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | 5.0-desired | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service arch 2020-06-29, Service arch 2020-07-13, Service Arch 2020-08-10, Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-09-21 | ||||||||
| Participants: | |||||||||
| Description |
|
In situations where a response from a mongod to a mongod or a mongos has a “code” field, we should pass the response through a helper function that munges it into ErrorExtraInfo and uses that ErrorExtraInfo as part of throwing a DBException. We can then use that type information to guide it through a different path in service infrastructure. In the immediate, it is most likely sufficient to encode the entire Egress Response BSONObj into the ErrorExtraInfo via functions analog to getStatusFromCommandResult(). |