Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
osX 10.10.4
mongo 3.0.3
*Location*: http://docs.mongodb.org/manual/core/index-intersection/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36
*Referrer*: http://stackoverflow.com/questions/24504792/mongodb-index-intersection
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: core/index-intersection
osX 10.10.4 mongo 3.0.3 *Location*: http://docs.mongodb.org/manual/core/index-intersection/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36 *Referrer*: http://stackoverflow.com/questions/24504792/mongodb-index-intersection *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: core/index-intersection
-
0.25
Description
I tried similar query example on "version" : "3.0.3"
there's no AND_SORTED stage or an AND_HASH stage. both winning plan and rejected plan uses single index.
The document is also too simple. I think a brief theoretical foundation introduction and how to hint the driver using index intersection is needed.
Best Regards