[SERVER-18679] Wrong key count for reverse indexes in WT Created: 27/May/15 Updated: 07/Dec/16 Resolved: 22/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Igor Canadi | Assignee: | David Hows |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
Steps to reproduce: ) will report that the index has 0 keys in "keysPerIndex" field, while the expected number would be 2 I suspect the problem is here: https://github.com/mongodb/mongo/blob/v3.0/src/mongo/db/storage/wiredtiger/wiredtiger_index.cpp#L288 We're locating minKey, although minKey is actually at the end for the reverse index. The same problem exists for RocksDB because I copied that part of the code |
| Comments |
| Comment by Githook User [ 15/Jun/15 ] |
|
Author: {u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}Message: |