[SERVER-17858] Partial indexes should support more complex queries Created: 02/Apr/15  Updated: 05/Feb/16  Resolved: 10/Jun/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.1.5

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-18327 Coverity analysis defect 72086: Unche... Closed
Related
related to SERVER-18308 Partial indexes should support point ... Closed
related to SERVER-17853 Allow more complex expressions to be ... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 3.1.2, Quint Iteration 3, Quint Iteration 4, Quint Iteration 5
Participants:

 Description   

The 3.1.1 release of partial indexes supports only provides support for simple user queries. It should be possible for more complex user queries to be answered by a partial index.

For example, an index with key pattern {a: 1} and partial index document filter {x: {$exists: true}} should be able to answer all of the following queries:

find({a: 1, x: {$in: [1, 2]}})
find({a: 1, $or: [{x: 1}, {x: 2}]})
find({a: 1, x: /hello world/})
find({a: 1, x: {$type: 1}})
find({a: 1, x: {$geoWithin: ...}})
find({a: 1, x: {$elemMatch: {y: 1, z: 1}}})



 Comments   
Comment by Max Hirschhorn [ 10/Jun/15 ]

All work completed in the different subtasks.

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