Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.6.0, 2.6.1-rc0
-
None
-
ALL
-
Description
In 2.4.10, tailable cursors seem to honor $maxScan values:
> db.tailable.find().addOption(DBQuery.Option.tailable)._addSpecial("$maxScan", 100).explain();
|
{
|
"cursor" : "ForwardCappedCursor",
|
"isMultiKey" : false,
|
"n" : 100,
|
"nscannedObjects" : 100,
|
"nscanned" : 101,
|
"nscannedObjectsAllPlans" : 100,
|
"nscannedAllPlans" : 101,
|
...
|
In 2.6 and 2.6.1-rc0, they do not:
> db.tailable.find().addOption(DBQuery.Option.tailable)._addSpecial("$maxScan", 100).explain();
|
{
|
"cursor" : "BasicCursor",
|
"isMultiKey" : false,
|
"n" : 10000,
|
"nscannedObjects" : 10000,
|
"nscanned" : 10000,
|
"nscannedObjectsAllPlans" : 10000,
|
"nscannedAllPlans" : 10000,
|
...
|