Implement set_key — in-memory pending key list

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines - Foundations
    • 546.393
    • SE Foundations - 2026-06-09
    • 5

      Background: WT-17535 introduced the set_key stub returning ENOTSUP. The key provider module needs to be able to push key data with an associated timestamp into WiredTiger and have it stored reliably until the next checkpoint consumes it. Multiple set_key calls may arrive between checkpoints, so all pushed entries must be retained in memory until a checkpoint determines which one to use.

      Currently set_key stores one key.

      Acceptance Criteria:

      • set_key stores pushed key data and timestamp in an in-memory pending list
      • Multiple entries can be held simultaneously
      • Timestamps must be monotonically increasing; error returned otherwise
      • Timestamp must be > global stable timestamp; error returned otherwise

      Depends on WT-17535.

            Assignee:
            Jie Chen
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: