Setting a new stable timestamp in the past doesn't throw an error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines
    • Megabat - 2024-05-14
    • 1

      Setting a new stable timestamp at an earlier point in the past (compared to the current stable timestamp) will be seemingly be "allowed" as this behaviour doesn't throw any errors, but internally nothing will be changed.

      This isn't strictly documented, and can be confusing. The scope of this ticket is to investigate into making this behaviour result in a failed assertion for illegal behaviour, as well as updating the documentation.

            Assignee:
            Etienne Petrel
            Reporter:
            Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: