Munge Egress Responses into a ErrorExtraInfo subclass

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • Fully Compatible
    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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().

            Assignee:
            Unassigned
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: