[SERVER-42456] Make it easier to access the ClusterClientCursor underlying a ClusterCursorManager::PinnedCursor Created: 26/Jul/19 Updated: 29/Oct/23 Resolved: 09/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-08-12, Query 2019-08-26 |
| Participants: |
| Description |
|
The ClusterCursorManager::PinnedCursor has a bunch of boring boilerplate because there is no easy way to access the cursor it owns. We should add a getter, an operator "->", or both to allow easier access to the underlying cursor and remove this boilerplate code; we already have these in mongod cursors |
| Comments |
| Comment by Githook User [ 09/Aug/19 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@10gen.com'}Message: |