Fixed test after fixed batch size usage.

[derickr]

No description provided.

[jmikola]

This is peculiar. Does it not inherit the batchSize from the original command, or is the command option only for the initial inline batch?

[bjori]

AFAICT from the spec, these batchsizes are completely independent.
Unless you set the batchsize after the initial command, it will default to the server default.

This does indeed seem a bit confusing but I think this fix is correct.

[bjori]

"The batch sizes for each getMore is an independant parameter from this and uses the normal getMore semantics of 0 meaning server default."

[derickr]

Correct.

[bjori]

Wait. I'm confused. Without explicitly setting the batchSize to 2 before the getmore, why does it say the cursor is dead right away?
It clearly isn't dead as you are continuing to read results from it.

[bjori]

Nevermind. This is just the way it is, and seems to have been for a while.

The cursor reports itself as dead after the "last getmore" (e.g. op_reply reports the cursor is no longer available after reading this batch).
I guess this makes sense :]

LGTM

[derickr]

Yeah, I don't like the original definition either, but it is what it is :-)