Use PIT timestamp for timeseries upgrade check in aggregation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-04-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When establishing a consistent collection for the timeseries upgrade check, we pass boost::none as the readTimestamp. This means we're not using the point-in-time read timestamp from the recovery unit, which can lead to inconsistent reads.

      Other callers of establishConsistentCollection in the same file (e.g., line 178-182 and line 776-779) already correctly retrieve the PIT read timestamp from the recovery unit via getPointInTimeReadTimestamp().

      The fix retrieves the PIT read timestamp and passes it to establishConsistentCollection.

            Assignee:
            Tommaso Tocci
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: