Schema operations are causing transactional failures

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: Transactions
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2025-11-21
    • 3

      I've hit an interesting edge case with WT_SESSION::create() and exclusive=true.
      Let's say I have a table already created table:collection-xyz. Then I have the following set of operations

      begin_transaction()
create("table:collection-xyz") --> EEXIST
drop("table:collection-xyz") --> OK
create("table:collection-xyz") --> OK
commit() --> EINVAL "transaction requires rollback"

      It looks like the error is being set in __wt_txn_err_set during the initial create call. Would it make sense to 'clear' the error, given the subsequent drop -> create?
       

       

            Assignee:
            Chenhao Qu
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: