-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: 8.0.19, 8.2.6
-
Component/s: None
-
Query Optimization
-
Fully Compatible
-
ALL
-
v8.3, v8.2, v8.0
-
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In some cases, clustered collections incorrectly return results that should be filtered out by the $lt operator. Specifically, this query:
db.clustered_repro.find({ _id: { $lt: 3 } }).sort({ _id: -1 })
May return a document with { _id: 3 }.
The same happens when using an aggregation pipeline. Removing the sort condition, using ascending sort, or changing to $lte, resolves the issue. But I could find no workaround without changing the query or using a plain collection.
- is related to
-
SERVER-127218 Create a PBT that tests clustered collection correctness
-
- Backlog
-
-
SERVER-75604 Eliminate CollectionScanNode.filter when not needed for clustered collection scans
-
- Closed
-
- related to
-
SERVER-124915 Add clustered_collection_bounded_scan.js to multiversion testing denylist
-
- Closed
-