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

Use WT_TIME_WINDOW in hs_rec.c

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.9.0, 4.4.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • 0
    • Storage - Ra 2020-11-30, Storage - Ra 2020-12-14

      This is a suggested change I have to simplify the history store code and ideally standardise how we pass information between functions in hs_rec.c. I'm happy for it to be declined if it seems unfeasible or not that helpful.

      In essence we have a number of fields we pass all over to pretty much every function in hs_rec they are:

      • btree id
      • key
      • start_time_point
      • stop_time_point
      • counter

      and maybe hs_value.

      If we could put those into a WT_HS_RECORD I think it would be a lot cleaner.

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: