-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 4.0.0
-
Component/s: Sharding
-
Labels:
-
Minor Change
-
ALL
-
Repl 2019-02-11, Sharding 2019-03-25, Sharding 2019-04-08
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
-
-
- Closed
-
- is documented by
-
DOCS-12608 Docs for SERVER-39175: Transactional bulkWrite error missing writeErrors (mongos)
-
- Closed
-
- related to
-
-
- Closed
-