-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
Query Optimization
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There is no obvious reason to disallow non-btree index usage with a $not expression. Several geo tests show that the planner is generating correct index bounds for queries containing $not and a geo index:
https://github.com/mongodb/mongo/blob/master/src/mongo/db/query/query_planner_geo_test.cpp#L965
https://github.com/mongodb/mongo/blob/master/src/mongo/db/query/query_planner_geo_test.cpp#L1085
- related to
-
SERVER-44011 Optimise queries with logical operators for compound hashed indexes
-
- Closed
-