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

Make prepare transaction work consistently with lower isolation levels.

XMLWordPrintableJSON

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Currently update on top of a prepared update will be successful using a transaction with "read_committed" isolation. But with a snapshot isolation transaction, this will return prepare_conflict error.
      The behaviour need to be consistent.
      eg:-

      session.begin_transaction("isolation=snapshot")
cursor.set_key(1)
cursor.set_value(1)
cursor.update()
session.prepare_transaction("prepare_timestamp=1")

session_1.begin_transaction("isolation=read-committed")
cursor_1.set_key(1)
cursor_1.set_value(2)
cursor_1.update() .  --> returns success, no prepare_conflict error. 
session_1.commit_transaction()

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: