-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.0
-
Component/s: Storage
-
Fully Compatible
-
ALL
-
-
TIG F (01/29/16), TIG 10 (02/19/16)
If a long index key (greater than 1024) is inserted into a collection (when the parameter failIndexKeyTooLong is set to false), then collection validate does not take it into account and fails. This seems to have been introduced from the work in SERVER-19521.
{ "ns" : "test.longindex", "nrecords" : 2, "nIndexes" : 1, "keysPerIndex" : { "test.longindex.$_id_" : 1 }, "indexDetails" : { "test.longindex.$_id_" : { "valid" : true } }, "valid" : false, "errors" : [ "number of _id index entries (1) does not match the number of documents (2)" ], "advice" : "ns corrupt. See http://dochub.mongodb.org/core/data-recovery", "ok" : 1 }
- is depended on by
-
SERVER-22231 Add additional test suites to run resmoke.py validation hook
- Closed
- is related to
-
SERVER-19521 validate should check consistency of number of index entries
- Closed