[SERVER-61779] Support cursors for transaction API exhaustive find Created: 29/Nov/21 Updated: 29/Oct/23 Resolved: 24/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2022-03-07, Sharding NYC 2022-03-21, Sharding NYC 2022-04-04 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
Currently, exhaustiveFind in the transaction API only allows finds with the singleBatch option set. To make the find useful for reads that can return more than one batch of data, we should update that method to detect when there is more than one batch (by checking the original response) and iterating the find's cursor until it's exhausted before returning to the caller. |
| Comments |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |