-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
Fully Compatible
-
ALL
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 SERVER-4150). However, in cases where some query plans are ordered and others are unordered, and a small limit is applied, this may result in an unordered plan being incorrectly reported at the top of explain when the results actually came from an ordered plan. We should take plan ordering and limit completion into account when choosing a plan to report at the top of explain (ExplainClauseInfo::virtualPickedPlan).
- is depended on by
-
SERVER-7950 MongoDB not using the most optimal index when sorting on 2 keys
- Closed
- is related to
-
SERVER-10026 New query system
- Closed
-
SERVER-10565 Re-implement explain() for new execution engine
- Closed
- related to
-
SERVER-8747 In explain output, per plan 'n' count is not updated after an out of order plan wins
- Closed