Operational Defect Database

BugZero found this defect 37 days ago.

MongoDB | 2640467

Time Series ascending sort by timestamp causes "BoundedSorter input is too out-of-order"

Last update date:

4/12/2024

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

We attempt to find the earliest timestamp in a timeseries collection. In a usual collection, you can write an aggregation with ascending $sort, $limit 1 and $project steps without issues. After migrating to a timeseries collection on Atlas, this fails with the following error: PlanExecutor error during aggregation :: caused by :: BoundedSorter input is too out-of-order: with bound 2024-03-28T19:00:00.000+00:00, did not expect input 2024-03-28T18:04:01.000+00:00 Further observations: The sort (aggregation) step works when you invert the sorting (descending).

Top User Comments


Steps to Reproduce

have a timeseries collection with different timestamps execute this aggregation: { timestamp: 1, } receive error message about BoundedSorter input is too out-of-order. Screenshot from Compass is attached.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Investigating

Learn More

Search:

...