[SERVER-36153] Remove SortedDataInterface::newRandomCursor() Created: 16/Jul/18 Updated: 29/Oct/23 Resolved: 31/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2018-08-13 |
| Participants: |
| Description |
|
SortedDataInterface::newRandomCursor() was implemented only by the MMAPv1 storage engine in order to implement storage-optimized $sample. Now that MMAPv1 is no longer supported, this method can be removed from the storage API. WiredTiger and other storage engines can still offer storage-optimized $sample support via RecordStore::getRandomCursor(). |
| Comments |
| Comment by Githook User [ 31/Jul/18 ] |
|
Author: {'username': 'dstorch', 'name': 'David Storch', 'email': 'david.storch@10gen.com'}Message: Only the MMAPv1 storage engine ever provided an |
| Comment by Ian Whalen (Inactive) [ 20/Jul/18 ] |
|
geert.bosch just a heads up that we're adding to Remove MMAPv1, but Storch is planning on doing this next sprint. |