-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
Affects Version/s: None
-
Labels:
-
Environment:official docker image, mongo:3.0.2
*Location*: https://docs.mongodb.com/v3.0/core/index-intersection/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
*Referrer*: https://docs.mongodb.com/v3.0/core/indexes-introduction/
*Screen Resolution*: 1440 x 900
official docker image, mongo:3.0.2 *Location*: https://docs.mongodb.com/v3.0/core/index-intersection/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 *Referrer*: https://docs.mongodb.com/v3.0/core/indexes-introduction/ *Screen Resolution*: 1440 x 900
From documentation
...
MongoDB can use the intersection of the two indexes to support the following query:
db.orders.find( { item: "abc123", qty:
{ $gt: 15 } } )
...
Based on that improvement and comment intersection should not work with range query. So the example should be like db.orders.find( { item: "abc123", qty:
{ $eq: 15 }} )
- related to
-
DOCS-9723 Use another query to trigger index intersection
-
- Closed
-