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.
- depends on
-
SERVER-38583 Transactional bulkWrite error missing writeErrors (mongod)
-
- Closed
-
- is documented by
-
DOCS-12608 Docs for SERVER-39175: Transactional bulkWrite error missing writeErrors (mongos)
-
- Resolved
-
- related to
-
-
- Needs Scheduling
-