[SERVER-4463] Allow covered index use for non-array fields in multi-key index Created: 09/Dec/11  Updated: 06/Dec/22  Resolved: 12/Jan/17

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

Type: Improvement Priority: Major - P3
Reporter: Chris Scribner Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4468 Keep track of multi-key fields in index Closed
Duplicate
duplicates SERVER-3173 Planner should use path-level multike... Closed
Related
is related to SERVER-15086 Allow for efficient range queries ove... Closed
Assigned Teams:
Query
Participants:

 Description   

Please allow this scenario to work for an indexOnly query.

doc: { _id: id, arr: [strings], i: integer}
index: { arr: 1, i: -1, _id:1 }
query: find({arr:val}, {_id:1}).sort({i:-1}).limit(...)

This is for a "full-text" search style feature.

Thanks, Chris



 Comments   
Comment by David Storch [ 12/Jan/17 ]

As far as I can tell, this is indeed a duplicate of SERVER-3173, so I am closing as such. As part of SERVER-15086, we extended the query system to persist more granular information about which fields/paths are multikey in the catalog. The path-level multikey metadata work allows us to implement this optimization, as well as other related optimizations (e.g. SERVER-2104). Please watch SERVER-3173 for further updates.

Comment by Jay Cliffe [ 03/Jul/13 ]

It feels related, but regardless it also feels very doable by the index and likely just a behavioral switch without structure modification. </hypothesizing>

Comment by Eliot Horowitz (Inactive) [ 23/Feb/12 ]

@brian - this isn't really related to SERVER-3173

Comment by Brian A. Smith [ 23/Feb/12 ]

Also a pain point for us.

Is this related to SERVER-3173?

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