Assert that a storage transaction is active for all cursor read operations

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Execution Team 2020-01-13
    • 9
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It is not incorrect to use WiredTiger cursors without an active transaction, however this can be problematic when operations have preconditions in flags passed to begin_transaction(). Without an active transaction, an operation may expect to ignore prepare conflicts, but not (see SERVER-44581).

      Like we do for writes, we should assert that cursor next() and seek() operations are performed inside an active transaction.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: