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

Search should not return onpage value if nothing is found by transaction read

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage Engines 2020-01-27, Storage Engines 2020-02-10

      Before durable history, we store the stable version in the disk image. The transaction read only traverse the update chain and the upper level search logic has the assumption that if nothing is found by transaction read, we should return the onpage value.

      This is no longer true in history store as we store the newest committed value on disk. To change that, we have modified transaction read to traverse the update chain, onpage value, then the update chain. However, we haven't removed the assumption in the upper level search logic that the onpage value should be visible if nothing is found. This problem is causing test_hs02 to fail.

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: