-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: 3.2.0-rc0
-
Query
The getMore command should not return a cursor id if the limit specified on the find command has been satisfied by the returned batch. But if the batch size specified on the getMore command gets you just to the limit, then a cursor id is still returned by mongos. A subsequent getMore will correctly return an empty batch and no cursor id.
This does not happen with mongod.
- duplicates
-
SERVER-19915 Cursor may indicate that it is not exhausted even though next getMore will close the cursor and return no results
- Backlog
- related to
-
CDRIVER-2736 Mongoc cursor error when running find_with_opts against a sharded cluster
- Closed