[SERVER-11889] Add new plan stats to explain output Created: 27/Nov/13 Updated: 28/Oct/15 Resolved: 13/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | 2.5.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa, explain, nqf, query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Problem: The various runners (SingleSolution, CachedRunner etc.) call getStats() in the getExplainPlan implementation. However, the details collection by each concrete implementation are not projected in the explain plan. This could provide core development/debug information as well as help customer support scenarios. Solution: To view the stats from the shell, use db.col.find().explain(true) Workaround: |
| Comments |
| Comment by Githook User [ 21/Jan/14 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by Githook User [ 13/Jan/14 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: |