Avoid redundant layered-level lookup for insert/update in leader mode

XMLWordPrintableJSON

    • Storage Engines - Transactions
    • 559.317
    • SE Transactions - 2026-06-05
    • 3

      In leader mode, the layered cursor performs a full layered-level lookup before insert/update with overwrite=false. This is redundant: leaders have no ingest constituent, all data is in the stable btree, and the btree cursor already enforces overwrite semantics (stable_cursor->update returns WT_NOTFOUND for missing keys; stable_cursor->insert returns WT_DUPLICATE_KEY for existing keys). The lookup should be skipped for leaders and the btree-level error returns used directly instead.

            Assignee:
            Chenhao Qu
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: