-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Go over the functionality around obtaining and closing history store cursor:
__wt_hs_cursor()
__wt_hs_cursor_close()
__wt_hs_cursor_open()
do we need is_owner argument to __wt_hs_cursor
do we need WT_HS_SESSION_FLAGS flag and __wt_hs_cursor() call to be callable again without calling a close.
The implementation was based on how LAS cursor calls looked like, then followed by a few rounds of changes along with the durable history project.
Once we are done with durable history, it will be worthwhile to revisit and clean up the history store cursor functions.
- duplicates
-
WT-5512 Create a new history store cursor type that inserts/deletes by directly putting updates on the page
- Closed