-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:Ubuntu 14.04, MongoDB 2.6.9
*Location*: http://docs.mongodb.org/manual/reference/operator/meta/maxTimeMS/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/reference/operator/meta/maxScan/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/operator/meta/maxTimeMS
Ubuntu 14.04, MongoDB 2.6.9 *Location*: http://docs.mongodb.org/manual/reference/operator/meta/maxTimeMS/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/reference/operator/meta/maxScan/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/operator/meta/maxTimeMS
The syntax given for maxTimeMS is incorrect and results in a query with an unlikely projection.
db.collection.find( { } ,
{ $maxTimeMS: 100 })
should be
db.collection.find( { $query: { }, $maxTimeMS: 100 } )
Reporter: Jon Anderson
E-mail: squiggs.jonny5@gmail.com