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

Define whether or not cursor reset can throw WT_ROLLBACK

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • StorEng - Defined Pipeline

      Until SERVER-81493, MongoDB made an assumption that WT_CURSOR::reset() would never return WT_ROLLBACK. That still appears to be true, but it's not well-defined in the API. We would like the WT API to explicitly tell us whether or not that is possible.

      We would prefer that reset() cannot throw WT_ROLLBACK, because we often reset cursors in destructors. Since we convert WT_ROLLBACK to WriteConflictExceptions, we risk crashing, since exceptions cannot be thrown in destructors.

            Assignee:
            backlog-server-storage-engines Backlog - Storage Engines Team
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:

                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.