Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
MongoDB 2.4.8
*Location*: http://docs.mongodb.org/manual/reference/database-profiler/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/search/?query=profiler
*Screen Resolution*: 2560 x 1440
*repo*: docs
*source*: reference/database-profiler
MongoDB 2.4.8 *Location*: http://docs.mongodb.org/manual/reference/database-profiler/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/search/?query=profiler *Screen Resolution*: 2560 x 1440 *repo*: docs *source*: reference/database-profiler
Description
The output reference on this page does not mention scanAndOrder, which is a very useful field in the profiling output.
See for example the explain() definition of scanAndOrder:
http://docs.mongodb.org/manual/reference/method/cursor.explain/#explain.scanAndOrder
Attachments
Issue Links
- depends on
-
SERVER-12136 scanAndOrder doesn't appear in profiler output in 2.5.x
-
- Closed
-