-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.5.4
-
Component/s: Querying
-
None
-
Query Optimization
-
Fully Compatible
Eliminate $in as a distinct match expression type. Re-implement as a series of $or clauses. This will support more aggressive optimizations in the query planning stage.
- is duplicated by
-
SERVER-9094 Optimize $or queries to perform like $in if all clauses are on the same field
- Closed
-
SERVER-14309 can't do non-multi update or upsert with single-value $in query predicate on shard key
- Closed
- is related to
-
SERVER-6001 key matching is not handled properly for the $elemMatch operator
- Closed
-
SERVER-10026 New query system
- Closed
-
SERVER-1205 $or sort does not use index ranges expressed in or clauses
- Closed
-
SERVER-9092 Allow for Binary prefixes, and more broadly, ranges in general, to be used as parts of $in queries.
- Closed
-
SERVER-14309 can't do non-multi update or upsert with single-value $in query predicate on shard key
- Closed
- related to
-
SERVER-5481 query on undefined field matches empty array
- Closed
-
SERVER-21065 Optimizer should consider predicate with "$in" operator having a single argument to be equivalent to the equality operator
- Closed