[SERVER-18884] Allow $in to be specified in partial index document filter Created: 09/Jun/15  Updated: 06/Dec/22  Resolved: 02/Oct/21

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Backlog - Query Optimization
Resolution: Duplicate Votes: 27
Labels: storch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-59508 Support $or, $in and multi-level expr... Closed
Related
related to SERVER-59508 Support $or, $in and multi-level expr... Closed
is related to SERVER-55782 Allow $regex to be specified in parti... Backlog
is related to SERVER-17853 Allow more complex expressions to be ... Backlog
Assigned Teams:
Query Optimization
Participants:
Case:

 Description   

Users should be able to specify the $in predicate operators as part of a partial index document filter.

For example:

db.collection.ensureIndex({a: 1}, {partialFilterExpression: {b: {$in: [1, 2, 3]}}});
db.collection.find({a: 1, b: 1}); // Should be able to use the above index. 



 Comments   
Comment by James Wahlin [ 02/Oct/21 ]

Work to support $in within partial indexes has been committed under SERVER-59508.

Comment by Katya Kamenieva [ 05/Apr/21 ]

I edited this one to represent $in and created SERVER-55782 for $regex

Comment by Evtim Georgiev [ 02/Apr/21 ]

Could we have the separate issues for $in and $regex logged so we could vote and watch the ones we are interested in? We could definitely use the $in support, that would help us a lot.

Comment by Katya Kamenieva [ 10/Nov/20 ]

Keeping this ticket in the backlog. This probably will be split into two separate items: one for $in, one for $regex, with $in having higher priority.

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