[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:
1. create a collection and a reverse index
2. insert two records into a collection
3. db.collection.validate(

{full:true}

) 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: SERVER-18679 Wrong key count for reverse indexes in WT
Branch: master
https://github.com/mongodb/mongo/commit/546e2943af3c9d0eb50062c26f52303452423f29

Generated at Thu Feb 08 03:48:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.