Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
ALL
-
Sharding 2019-01-14
Description
Any error encountered in a batch during a transaction is thrown by mongos and mongod (because a transaction cannot succeed if any write fails) leading to a command error instead of individual write errors in the response to the client. However, currently mongos does not throw targeting errors encountered in a transaction batch, leading to a response with a write error instead. For consistency, mongos should throw these errors.
Attachments
Issue Links
- related to
-
SERVER-38570 txn_override.js should also abort when writeError is not empty
-
- Closed
-
-
SERVER-43468 Complete TODO listed in SERVER-38690
-
- Closed
-