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

turn key consistent checking on for MongoDB builds

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage - Ra 2022-03-21

      In WT-8691, we removed the key_consistent write timestamp usage keyword.

      A side-effect of that change was to enable more key-consistency checking for the ordered keyword than before, which broke the MDB build.

      WT-8748 reverted the change to add additional checking, this ticket is a reminder to add the additional checking back in to MDB server builds if/when that's possible.

      The change is in txn/txn.c, where we now only run some of the key-ordering checks if the WT_STANDALONE_BUILD flag is defined, which limits the checks to WiredTiger's internal testing, and not MDB server runs. See the WT-8478 commits for the details.

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: