-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance, Querying
Update:
Index intersection is on by default. The query planner currently limits itself to 2 indices at a time, though this limit may increase in the future.
Original Text:
This should support both single and multiple index intersections.
This should support queries that which want to use a covered index; then complex intersections would never need to hit the document to return the values.
A more detailed description of index intersection in a traditional RDMS can be found here:
http://www.sql-server-performance.com/2003/index-intersection/
- depends on
-
SERVER-3414 consider using nscannedObjects in addition to nscanned when selecting a query plan
- Closed
- is depended on by
-
SERVER-4572 Geospatial index cannot be used in $and criteria of a query?
- Closed
- is duplicated by
-
SERVER-7742 Improve the way indexes are used to do a range query on one field and sort on another
- Closed
-
SERVER-8753 Query optimizer doesn't use hashed key in a query with sorting on a different indexed value
- Closed
-
SERVER-3118 get best intersection match via query
- Closed
-
SERVER-8768 implement support for interleaving btree and non btree cursors in query optimizer cursor selection code
- Closed
-
SERVER-8140 Compound Index with 2d and Text
- Closed
- related to
-
SERVER-1000 $all with query optimizer
- Closed
-
SERVER-9148 In text searches with $near filter, results don't obey filter
- Closed
-
SERVER-8790 Introduce composable "stages" in query execution
- Closed