Improve the error message of WT_UNCOMMITTED_DATA

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - 2025-08-29
    • 1

      WT-10576 has introduced a transaction visible_all check on the last modified transaction on the file as part of the drop operation before performing the drop to avoid the race conditions of other sessions operating on the same file.

      Later, as part of the sublevel error code, the error message WT_UNCOMMITTED_DATA is added, and it is being returned whenever a drop operation fails due to this transaction visible_all reason.

      This message is confusing the user, as it says that the failure is due to the uncommitted data, but actually there is no uncommitted data present in that file. Improve the error message as `Table's last modified transaction is not yet globally visible` along with the error macro to WT_FILE_MAX_TXN_NOT_GLOBALLY_VISIBLE`.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Haribabu Kommi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: