-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 1.34.1
-
Component/s: Aggregation pipeline, Atlas, CRUD, Embedded Shell
-
None
-
Environment:Fedora linux, compass git tag v1.34.1 built on host, local mongodb server (v6.1.0) and also MongoDB Atlas server.
-
5
Problem Statement/Rationale
Aggregation stage ...
{$limit: 9223372036854775807}
... doesn't work - there is an error reported.
{$limit: 9223372036854775295}
... seems to be the maximum number that does not produce an error, although, I'm not confident that number is actually sent to the server. I observed port 27017 packets with wireshark and noted unusual 64-bit numbers being sent to the server for the $limit value. Packets sent by pymongo looked normal and expected.
Steps to Reproduce
Enter $limit stage as above and observe error.
Expected Results
Accept 2^63-1 as valid $limit value
Actual Results
Error message
Additional Notes
This bug also applies to mongosh, the mongosh in compass, and MongoDB Atlas aggregation.
This bug does NOT appear in pymongo.
- is related to
-
NODE-3391 EJSON.stringify does not stringify Long values properly
-
- Backlog
-
-
COMPASS-4884 Exporting collections with int64 results in wrong (rounded) values
-
- Closed
-