-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Windows 7
*Location*: http://docs.mongodb.org/manual/tutorial/analyze-query-plan/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/core/query-optimization/
*Screen Resolution*: 1366 x 768
*repo*: docs
*source*: tutorial/analyze-query-plan
Windows 7 *Location*: http://docs.mongodb.org/manual/tutorial/analyze-query-plan/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/core/query-optimization/ *Screen Resolution*: 1366 x 768 *repo*: docs *source*: tutorial/analyze-query-plan
Below statement is incorrect:
winningPlan.stage.inputStage.stage displays IXSCAN to indicate index use.
The bold part should be
winningPlan.inputStage.stage
It has an extra "stage" after winningPlan.