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

Return WT_PREPARE_CONFLICT only for read not write operations

    • Type: Icon: Documentation Documentation
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • WT11.0.0, 5.3.0
    • Affects Version/s: None
    • Component/s: None

      The following is the description of the WT_PREPARE_CONFLICT.

      #define WT_PREPARE_CONFLICT

      Conflict with a prepared update.

      This error is generated when the application attempts to update an already updated record which is in prepared state. An updated record will be in prepared state, when the transaction that performed the update is in prepared state.

       

      **This error never occurred in my test with update of a record that is already updated by a transaction which is in prepared state. It always produces the error of "conflict between concurrent operations". But the WT_PREPARE_CONFLICT error is raised when the record is read and it is true also as per the description in the following link.

      http://source.wiredtiger.com/3.2.0/transactions.html#transaction_timestamps

       

      The documentation of the error needs an update from update to read in the following sections

      http://source.wiredtiger.com/3.2.0/error_handling.html

      **http://source.wiredtiger.com/3.2.0/group__wt.html#ga62f73045c5d37d8daee4533dd720376e

       

       

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: