-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.0.2
-
Component/s: None
-
Query Integration
-
Minor Change
-
ALL
-
-
QI 2023-11-27
-
(copied to CRM)
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.
- 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 related to
-
DRIVERS-3009 Ensure findOne does not set batchSize=1
- Implementing
-
NODE-6435 Remove `batchSize` as a findOne option and don't set batchSize on the cursor
- Closed
- 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