Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
3.4.6
-
None
-
Tested on Windows and Linux with MongoDB 3.4.6
-
ALL
-
Description
We have discovered an issue that we think related to the $sort + $limit optimizer.
We have attached dump of a sample collection.
Second query with a limit of 25 has as first element the last element of the first page (25th) instead of the 26th correct one.
Same queries performed without limit works properly.
Attachments
Issue Links
- duplicates
-
SERVER-28195 $skip followed by $limit in aggregation resort & lost records when $sort by equal values
-
- Closed
-