[SERVER-23921] audit the use of SortedDataInterface::Cursor::seek for full index traversal in our tests Created: 25/Apr/16 Updated: 04/Sep/19 Resolved: 04/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.3.5 |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Haley Connelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2019-09-09 |
| Participants: |
| Description |
|
There are a number of places where we traverse an index by seeking to kMinBSONKey:
This is correct only for non-compound indexes and may confuse future readers who may want to use it for traversing a generic index. Whenever possible, we should seek to BSONObj() instead of kMinBSONKey; this will seek to the leftmost document in the index, regardless of the index type. |
| Comments |
| Comment by Githook User [ 04/Sep/19 ] |
|
Author: {'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com', 'name': 'Haley Connelly'}Message: |