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

Review and cleanup history store cursor internal functions

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: