Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-89346

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

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • ALL
    • Hide
      1. have a timeseries collection with different timestamps
      2. execute this aggregation:
      {
        timestamp: 1,
      } 
      1. receive error message about BoundedSorter input is too out-of-order. Screenshot from Compass is attached.
      Show
      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.

      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).

            Assignee:
            chris.wolff@mongodb.com Chris Wolff
            Reporter:
            christoph.ahlers@vaillant-group.com Christoph Ahlers
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: