ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines - Transactions
    • 50.864
    • SE Transactions - 2026-12-04
    • None

      Move the bounds API fixes currently included in PR #15102 into a separate change, keeping WT-18717 focused on merge-based prepare-conflict handling.

      A layered cursor can retain a constituent’s position after returning a prepare conflict. Bounds handling should reject setting bounds in that state, preserve the existing range when a bound change is rejected, and continue to allow clearing bounds.

      Scope:

      • Extract the bounds-specific changes in __clayered_bound() and the corresponding architecture documentation.
      • Move the regression coverage in test_layered_prepare13.py, including forward/reverse comparisons against ordinary cursors.
      • Verify rejection of bound updates after prepare conflicts, preservation of existing bounds after rejected changes, and successful clearing of bounds.
      • Validate the bounds fix independently and confirm that removing it from WT-18717 preserves the core merge/retry behavior.

      The merge algorithm, retained-position retry handling and bounded initial-iteration conflict recovery remain in WT-18717.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Ravi Giri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: