[DOCS-12608] Docs for SERVER-39175: Transactional bulkWrite error missing writeErrors (mongos) Created: 09/Apr/19  Updated: 13/Nov/23  Resolved: 29/Aug/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.10, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-39175 Transactional bulkWrite error missing... Closed
Participants:
Days since reply: 4 years, 23 weeks, 6 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

Write errors while in a transaction is now reported as part of the write error field as opposed to the top level error. This is true for both mongod and mongos. Because of how we aggressively bail out early when encountering an error during a transaction, it is now possible (for the first time, I think) for (# of writeError + # of writeSucceeded) < nWritesInRequest, even for unordered writes.

Engineering Ticket 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.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 29/Aug/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12608: 4.2 BulkWriteError in txns
Branch: master
https://github.com/mongodb/docs/commit/1089bced30cc283422b751cca4bb102be4355d84

Generated at Thu Feb 08 08:05:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.