[SERVER-44698] Provide a DBClientCursor API to consume a whole batch in one shot Created: 18/Nov/19 Updated: 06/Dec/22 Resolved: 26/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Sprint: | Repl 2019-12-16 |
| Participants: |
| Comments |
| Comment by Lingzhi Deng [ 26/Nov/19 ] |
|
Closing as "Won't Fix" because I think using more(), next() and isDead() is sufficient to determine whether there are more documents for consumption. For metadata, we can use setReplyMetadataReader() on DBClientConnection to read metadata on a per-batch basis. |