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

Add an API to enforce consistent use of timestamps (#3667)

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc0, WT3.0.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage 2017-10-02, Storage 2017-10-23

      Splitting this out from WT-3565. daniel.gottlieb would like an API that can be set on tables so that incorrect usage can be detected as early as possible.

      This config setting would be allowed on WT_SESSION::create (and probably changeable via WT_SESSION::alter). We want something that allows for other additions in the future. It will be a config setting that is something like: assert=(timestamps=always|never|none).

      A setting of always means that every update of this table must be done in a transaction that uses timestamps. A setting of never means no update should ever be part of a transaction that uses timestamps. A setting of none mean no verification of usage should occur and would be the default as well as the setting for any table that is used in different ways at different times.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: