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

Transactional bulkWrite error missing writeErrors (mongos)

    XMLWordPrintable

Details

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

    Description

      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.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38583 Transactional bulkWrite error missing writeErrors (mongod)

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-12608 Docs for SERVER-39175: Transactional bulkWrite error missing writeErrors (mongos)

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-43492 Unblack list tests marked with SERVER-39175

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              randolph@mongodb.com Randolph Tan
              jesse@mongodb.com A. Jesse Jiryu Davis
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: