Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-24012

Clean up WriteConcernErrorDetail class and use it instead of a Status where appropriate

    XMLWordPrintableJSON

Details

    • Replication
    • Sharding 16 (06/24/16), Repl 2016-11-21

    Description

      Currently the getWriteConcernStatusFromCommandResult function returns a Status, but that loses some information includes in a write concern response, such as the 'errInfo' field.

      We should make WriteConcernErrorDetail easier to construct and parse from BSON, then use it anywhere we deal with write concern error responses (such as in Shard::CommandResponse)

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: