[SERVER-80794] Support iterating through bulkWrite response cursor for internal transactions Created: 06/Sep/23 Updated: 11/Sep/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
There is now a helper function to run bulkWrite request under an internal transaction. The bulkWrite command returns a cursor in its response. For the case where the response cursor isn't immediately exhausted (i.e. cursor id != 0), we must add logic to iterate through the response cursor in the transaction api helper. This only helps bulkWrite used in internal transactions. I think it is ok to punt on this until we have real use cases to run big enough bulkWrite in internal transactions that actually requires multiple response batches. |