[SERVER-19708] Should have separate RecordCursor and SeekableRecordCursor Created: 31/Jul/15 Updated: 19/Sep/15 Resolved: 28/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QuInt 8 08/28/15 |
| Participants: |
| Description |
|
A number of RecordCursor method do not apply for all cursors (for example seekExact does not apply for cursors obtained through getCursorForRepair). Rather than documenting that it is not allowed to call certain methods, it would be better to enforce this by using separate types. |
| Comments |
| Comment by Githook User [ 28/Aug/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |