-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-05-29, Repl 2023-06-12, Repl 2023-06-26, Repl 2023-07-10, Repl 2023-08-07, Repl 2023-08-21
Currently mongos forwards error responses to the client but doesn't do the same for successful responses in a bulk write request. For example, if an update in a bulk write fails with DuplicateKey, this error is returned to the client. However, if the update succeeds, then the response to the client is simply ok: 1, idx: <index> instead of having the nModified, n, value fields as well.
We need to attach these too to the response mongos give the client. We may also need to write logic to aggregate the response values as they may come from multiple shards.
- depends on
-
SERVER-72792 Implement progress bookkeeping for individual ops in BulkWriteExec
- Closed
-
SERVER-73281 Support update/delete op type to bulkWrite command on mongos
- Closed
- is related to
-
SERVER-79510 Always store BulkWriteReplyItems for WriteOps, even when they fail
- Closed