Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
7.0.2
-
None
-
Query Integration
-
Minor Change
-
ALL
-
-
QI 2023-11-27
Description
When using a TimeSeries collection if a find command has batchSize:1 and singleBatch:true the cursor returned is not closed, it reports a non-zero id. If the batchSize is omitted then the cursor will be closed. The same behavior is not observed for a typical collection, the id returned is always zero when singleBatch is set.
Attachments
Issue Links
- is depended on by
-
COMPASS-7462 Investigate changes in SERVER-82274: singleBatch find on a timeseries collection does not close cursor if batchSize is set
-
- Closed
-
- is documented by
-
DOCS-16499 Investigate changes in SERVER-82274: singleBatch find on a timeseries collection does not close cursor if batchSize is set
-
- Backlog
-
- related to
-
SERVER-80713 ID on exhausted cursor no longer 0
-
- Closed
-
-
NODE-5691 findOne on a timeseries collection leaks ClientSession
-
- Closed
-
-
SERVER-83077 Check one getNext beyond batchSize for EOF so we only return a cursor if there are more results
-
- Closed
-