[SERVER-7945] use plan ordering when reporting "winning" plan at the top of explain Created: 14/Dec/12 Updated: 11/Jul/16 Resolved: 13/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 1 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
In cases where there is no "winning" query plan, one query plan with the highest match count is reported in the explain output (see discussion in |
| Comments |
| Comment by Benety Goh [ 13/Feb/14 ] | ||||||||||||
|
plans are now ordered by ranking score computed in src/mongo/db/query/plan_ranker.cpp. | ||||||||||||
| Comment by Aaron Staple [ 15/Dec/12 ] | ||||||||||||
|
Test
|