[SERVER-44582] Assert that a storage transaction is active for all cursor read operations Created: 12/Nov/19 Updated: 06/Dec/22 Resolved: 07/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | groomed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Sprint: | Execution Team 2020-01-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 9 | ||||||||||||||||
| Description |
|
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 Like we do for writes, we should assert that cursor next() and seek() operations are performed inside an active transaction. |
| Comments |
| Comment by Louis Williams [ 07/Apr/20 ] |
|
|