-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.2.2
-
Component/s: Index Maintenance, Querying
-
None
-
Environment:Ubuntu 12.04, 12.10
-
ALL
-
Given the index
{
"v" : 1,
"key" :
,
"ns" : "accounts.calls",
"name" : "pricings.parent_id_1_start_at_1"
}
The query
{
"start_at":
,
"pricings.parent_id": 4
}
fails to use the upper bounds for start_at.
The explain() is;
{
"cursor" : "BtreeCursor pricings.parent_id_1_start_at_1",
"isMultiKey" : true,
"n" : 2526,
"nscannedObjects" : 349468,
"nscanned" : 349468,
"nscannedObjectsAllPlans" : 349468,
"nscannedAllPlans" : 349468,
"scanAndOrder" : false,
"indexOnly" : false,
"nYields" : 0,
"nChunkSkips" : 0,
"millis" : 550,
"indexBounds" :
,
"server" : "onatopp:27017"
}
- duplicates
-
SERVER-4180 Allow multiple constraints (on same field) within a $elemMatch clause to be used with a multikey index
- Closed