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

Support reading modify type updates in the history store for non-timestamp tables

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT10.0.0, 4.4.0-rc4, 4.7.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      Storage - Ra 2020-05-04
    • Backport Requested:
      v4.4

      Description

      The current logic informing full update from the history store modify updates are not handled for non-timestamp tables. The code needs to be fixed as below to handle it for non-timestamp tables.

      Read / update type Full / standard update Modify
      With timestamp Ordinary read would find the right value in history if tombstones / stop time pairs used normal visibility rules Ordinary read finds the oldest modify, uses its stop timestamp to skip forwards
      Without timestamp Ordinary read would find the right value in history Could use the same trick as above if extended to use the stop time pair (stashing the application's snapshot info, setting snap_min = snap_max = stop_txn and snapshot_count = 0.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              luke.pearson Luke Pearson
              Reporter:
              haribabu.kommi Haribabu Kommi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: