Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
7.0.0
-
None
-
Query Execution
-
ALL
-
Description
Hi,
First thanks for the great job with releasing MongoDB 7.
Maintaining some tools around MongoDB, we can see that the ID of exhausted cursor is no longer indicated as 0.
I cannot see any specific note about it in the changelog/driver compatibility documentation?
Is it an intended behaviour (for now that raises as a bug for us) ?
If yes how can we detected that such cursor is exhausted?
Attachments
Issue Links
- duplicates
-
SERVER-57067 [SBE] Find command unexpectedly returns cursorId when final batch size aligns with result set size
-
- Closed
-
- is related to
-
SERVER-82274 singleBatch find on a timeseries collection does not close cursor if batchSize is set
-
- Closed
-