[SERVER-83842] Clean up operation context parameters on storage functions Created: 04/Dec/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-83920 Take recovery unit for WT cursor help... Closed
depends on SERVER-83943 Remove operation context from WiredTi... Closed
depends on SERVER-83944 Take recovery unit for WT util functions Closed
depends on SERVER-83948 Take recovery unit for WiredTigerCursor Closed
depends on SERVER-83949 Take recovery unit for WT index util ... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2024-01-08, Execution Team 2024-03-04
Participants:

 Description   

There are many storage-related functions (for instance functions on KVEngine, RecordStore, SortedDataInterface, etc) which take an operation context but either do not use it at all or only use it to access the recovery unit. In the name of improved modularity, it would be good to clean up these functions to remove the operation context parameter or replace it with a recovery unit parameter instead.


Generated at Thu Feb 08 06:53:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.