[SERVER-77004] Mongos should forward reply items in bulk write operations to client Created: 10/May/23 Updated: 29/Oct/23 Resolved: 08/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2023-05-29, Repl 2023-06-12, Repl 2023-06-26, Repl 2023-07-10, Repl 2023-08-07, Repl 2023-08-21 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 08/Aug/23 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |