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

Test that using WT_CURSOR::modify works with all visibility scenarios

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.3 Required
    • Component/s: None
    • Labels:
      None

      Description

      The WT_CURSOR::modify API is a bit unusual, in that an update chain will build upon previous entries to create a full version of a value. We should add testing to ensure that WT_CURSOR::modify works as expected when used with unusual timestamp rules. Including if interleaving timestamp and non-timestamped updates, and adding timestamped updates out of order.

      This is follow on from WT-4776

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                backlog-server-storage-engines Backlog - Storage Engines Team
                Reporter:
                alexander.gorrod Alexander Gorrod
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: