[SERVER-72794] Implement cursor response for bulkWrite on mongos Created: 12/Jan/23 Updated: 29/Oct/23 Resolved: 17/Apr/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: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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-03-06, Repl 2023-03-20, Repl 2023-04-03, Repl 2023-04-17, Repl 2023-05-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
After waiting for responses for each sub-batching bulkWrite from shards, mongos needs to leverage existing response/progress bookkeeping logic in WriteOp in order to be able to reassemble the final client response from shards. |
| Comments |
| Comment by Githook User [ 17/Apr/23 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |