Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: 3.2.0-rc0
Component/s: Querying, Sharding
Labels:
- query-44-grooming

Assigned Teams:

Query
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Backlog - Query Team (Inactive)
Reporter:: Jeffrey Yemin
Participants:: Backlog - Query Team, David Storch, Jeffrey Yemin
Votes:: 1 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Oct 23 2015 02:02:38 AM UTC
Updated:: Dec 06 2022 04:41:23 AM UTC
Resolved:: Aug 02 2019 02:20:31 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates