Move truncate-related fields out of the layered table into a separate structure

XMLWordPrintableJSON

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

      Scope: move the truncate-related fields out of the layered table (WT_LAYERED_TABLE) into a separate structure.

      Why we do this — a step toward giving the layered-cursor per-operation context (WT_CLAYERED_OP) and its internal functions only the state they actually need, not the whole table or cursor:

      • Don't hand functions more information than they use — the op can then carry the truncate list, not the full WT_LAYERED_TABLE.
      • Simplify unit testing of layered cursors: a self-contained WT_CLAYERED_OP can be exercised directly, without mocking the entire layered table.

            Assignee:
            Ivan Kochin
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: