[SERVER-8871] Support admin hints per query pattern Created: 06/Mar/13 Updated: 27/Oct/15 Resolved: 15/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Diagnostics, Logging, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 2 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
The query optimizer currently generates a query plan which is cached and re-used based on the normalized "shape" of the query predicate and sort criteria.
|
| Comments |
| Comment by Githook User [ 15/Jan/14 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 07/Jan/14 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 19/Dec/13 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 18/Dec/13 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Aaron Staple [ 06/Mar/13 ] |
|
The ability to configure a persistent hint based on the query pattern sounds useful and I believe is unique to this ticket. Adding reporting info for the query optimizer's plan selection behavior also sounds useful. I think there is some overlap between this and the three other tickets listed in the "related to" section which also describe ways of accessing this information. When we spec out what we want to implement, we may want to consolidate these tickets. |