[SERVER-12469] Allow subdocuments to be used in covered indexes Created: 24/Jan/14 Updated: 10/Dec/14 Resolved: 10/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sylvain Zimmer | Assignee: | David Storch |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
eI'm familiar with the limitations of covered queries. Namely, from the docs (http://docs.mongodb.org/manual/tutorial/create-indexes-to-support-queries/#indexes-covered-queries) :
As a user this is really frustrating and doesn't make a lot of sense. I'm sure there may be internal design reasons, but is there really a theoretical reason it is not possible? This limitation is forcing us to dramatically change our schema design by migrating such fields off subdocuments. It is making us loose one of the main benefits of MongoDB so I would really like to see this limitation lifted, if possible. Thanks a lot! |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 10/Mar/14 ] |
|
Thanks hbcheng! Couldn't find that issue when I was looking earlier. |
| Comment by Hao Cheng [ 09/Mar/14 ] |
|
Is this the same issue as https://jira.mongodb.org/browse/SERVER-2104? That one is marked in "Planning Bucket A" It might help to vote for the aforementioned issue to push it higher on the priority list. I am also watching this issue as it would allow me to simplify my index and query design significantly. |
| Comment by Sylvain Zimmer [ 09/Mar/14 ] |
|
Can someone help? Thanks. |