findAndModify on a timeseries collection ignores the sort

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • ALL
    • v9.0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Enabled in SERVER-113969. The sort is not applied correctly on the bucket documents. The sort is still on the measurement field but applied to the bucket document, so the sort cannot be applied since the measurement field doesn't exist in the bucket document.

      However, our tests pass because the bucket rounding made it look like the sort was being applied. The bucket with the lowest value of f also had the lowest value of control.min.time so it was scanned first because the minimum timestamp is encoded in the _id of the bucket. If we move all of the measurements into the same bucket, then the sort does fail.

            Assignee:
            Unassigned
            Reporter:
            Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: