Require the step-down schema epoch alongside the step-down timestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Foundations
    • 444.837
    • None
    • None

      Background

      WT-18276 added the step_down_disaggregated_schema_epoch configuration to WT_CONNECTION::set_timestamp, declaring the step-down boundary in schema-epoch space alongside the timestamp. To let the server adopt the new parameter on its own schedule, supplying it is currently optional: a step-down timestamp without the epoch is accepted even when schema epochs are in use, and the epoch-space enforcement is simply skipped.

      Task

      Once the server passes the epoch with every step-down timestamp, make it required: setting step_down_timestamp without step_down_disaggregated_schema_epoch while schema epochs are in use should return EINVAL. The validation site carries a FIXME referencing this ticket.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: