[SERVER-28587] MongoDB aggregation query slowness Created: 03/Apr/17 Updated: 31/May/17 Resolved: 07/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 3.2.8 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Srikanth M | Assignee: | Mark Agarunov |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Will MongoDB use Index Intersection during the execution of aggregate query? Or, is the database engine bound to use a maximum of 1 index per query except in the case of $or operations? |
| Comments |
| Comment by Mark Agarunov [ 07/Apr/17 ] |
|
Hello medikosr, Thank you for the report. While MongoDB does support index intersection, it currently isn't generally used. This issue looks to be the same as those described in SERVER-22741 and SERVER-13740, so I've closed this as a duplicate. Please follow those issues for any updates on this issue. Thanks, |