[SERVER-28582] why Mongo DB only take one index at a time then its bad for multiple filter together placed Created: 01/Apr/17 Updated: 03/Apr/17 Resolved: 03/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ricky Sharma | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
why Mongo DB only take one index at a time then its bad for multiple filter together placed, because if a site that have 100+ filter to search result then we have to create a set of compound index combination that matches with the filter combination...its not a smart way . i using this in a project and almost 3 days gone but performance issue still remain. |
| Comments |
| Comment by Ramon Fernandez Marina [ 03/Apr/17 ] |
|
Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. I see you've already found the right forum to post questions like this one, so I'm going to close this ticket. Regards, |