[DOCS-950] Document index bound improvements for elemMatch query on multikey index Created: 04/Jan/13  Updated: 16/Mar/15  Resolved: 08/Oct/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.12

Type: Improvement Priority: Major - P3
Reporter: siddharth.singh@10gen.com Assignee: Kay Kim (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates DOCS-2703 Doc index bounds behavior for multike... Closed
Participants:
Days since reply: 11 years, 6 weeks, 5 days ago

 Description   

Our old behavior was that if two indexed field paths shared a common prefix, then only the first of those field paths appearing in the index would have its index bounds used for the query. With this ticket, if the index bounds for the two field paths come from the same $elemMatch clause then the index bounds on both field paths are used for the query.

See SERVER-3104 for more details.



 Comments   
Comment by siddharth.singh@10gen.com [ 04/Jan/13 ]

Note that this optimization is only applied if the field names within the $elemMatch are undotted. There are some cases where the optimization does not work correctly if the fields are dotted, described in SERVER-7509.

Generated at Thu Feb 08 07:39:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.