[SERVER-12024] re-implement $in in terms of $or Created: 10/Dec/13  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Querying
Affects Version/s: 2.5.4
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-9094 Optimize $or queries to perform like ... Closed
is duplicated by SERVER-14309 can't do non-multi update or upsert w... Closed
Related
related to SERVER-5481 query on undefined field matches empt... Closed
related to SERVER-21065 Optimizer should consider predicate w... Closed
is related to SERVER-6001 key matching is not handled properly ... Closed
is related to SERVER-10026 New query system Closed
is related to SERVER-1205 $or sort does not use index ranges ex... Closed
is related to SERVER-9092 Allow for Binary prefixes, and more b... Closed
is related to SERVER-14309 can't do non-multi update or upsert w... Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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.



 Comments   
Comment by Tudor Aursulesei [ 16/Mar/17 ]

https://jira.mongodb.org/browse/SERVER-14309 seems to depend on this ticket.

Generated at Thu Feb 08 03:27:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.