Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4405

Fix cursor next and prev for prepared transactions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.5, 4.1.6, WT3.2.0
    • Component/s: None
    • Story Points:
      5
    • Sprint:
      Storage Engines 2018-11-05, Storage Engines 2018-11-19

      Description

      To fix cursor next / prev behaviour when they encountered prepared updates resulting from insert / update / remove operations.

      Behaviorally, we went had a few iterations about what the expected state of a cursor should be after WT_PREPARE_CONFLICT is returned. We ended up choosing the following semantic:

      Have the cursor remain on the item when prepare conflict is returned, but handle subsequent move operations correctly in all scenarios: aborted, committed and visible, committed and not visible, at the start and end of the tree.
      For read-uncommitted transactions, the prepare conflict return needs to be considered as changing the position of the cursor - otherwise changing traversal direction after a prepare conflict can result in out of order cursor returns.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vamsi.krishna Vamsi Boyapati
                Reporter:
                vamsi.krishna Vamsi Boyapati
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: