Transactional bulkWrite error missing writeErrors (mongos)

XMLWordPrintableJSON

    • Minor Change
    • ALL
    • Repl 2019-02-11, Sharding 2019-03-25, Sharding 2019-04-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Followup to SERVER-38583: when a write error occurs in a multi-statement transaction, report the error in the same format as if it failed outside of a transaction. Today, the mongos reply for write error in a transaction includes ok: 0 and the error is at the top level. It should reply with include ok: 1 and a writeErrors array, the same as it does outside a transaction.

        1. SERVER-39175.patch
          8 kB

              Assignee:
              Randolph Tan
              Reporter:
              A. Jesse Jiryu Davis
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: