Details
-
Improvement
-
Resolution: Done
-
Blocker - P1
-
None
-
mongodb 2.4
*Location*: http://docs.mongodb.org/manual/reference/operator/query-modifier/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.48 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/reference/operator/meta/maxScan/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: reference/operator/query-modifier
mongodb 2.4 *Location*: http://docs.mongodb.org/manual/reference/operator/query-modifier/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.48 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/reference/operator/meta/maxScan/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: reference/operator/query-modifier
Description
The docs for $maxScan implies it has the same function as cursor.limit.
In practice it looks like $maxScan is a hard limit on how many docs mongodb will churn through to get results but cursor.limit will limit the output of the query (no matter how many documents are scanned).