[SERVER-26113] explain() for aggregations pulls from the plan cache Created: 14/Sep/16 Updated: 30/Apr/19 Resolved: 21/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris Harris | Assignee: | Nicholas Zolnierz |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Run the following four commands (the last command is repeated twice):
Output of the second .explain() in 3.2.9 is:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Query 2017-03-27 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) |
| Description |
|
Running an explain for an aggregation pipeline appears to get its output from the plan cache. This is evident by the fact that the first stage in the winning plan is CACHED_PLAN and there are no rejected plans. This seems contrary to documented behavior. This was observed on version 3.2.9 and 3.3.8. |
| Comments |
| Comment by Githook User [ 21/Mar/17 ] |
|
Author: {u'username': u'nzolnierzmdb', u'name': u'Nick Zolnierz', u'email': u'nicholas.zolnierz@mongodb.com'}Message: Small change to bug fix, and adding explain.js test. Formatting changes Missed formatting Incorporating CR feedback |