Put key_consistent back into the write_timestamp_usage choice table for backward compatibility

XMLWordPrintableJSON

    • None
    • None
    • v5.3

      When running compatibility tests as part of WT-8490, I ran into the below failure about the invalid argument 'key_consistent'. 

      [2022/02/03 07:53:09.835] develop/build/wt verifying mongodb-5.0 access method row...
      [2022/02/03 07:53:09.835] develop/wt dump and load mongodb-5.0 access method row...
      [2022/02/03 07:53:14.017] t: btree.prefix=0: WARNING, ignoring unknown configuration keyword
      [2022/02/03 07:53:14.017] [1643874794:17814][65512:0x7f3fd9a58b80], wt, WT_SESSION.create: [WT_VERB_DEFAULT][ERROR]: config_check, 165: Value 'key_consistent' not a permitted choice for key 'write_timestamp_usage': Invalid argument
      [2022/02/03 07:53:14.018] wt: table:wt: session.create: Invalid argument 

      The 'key_consistent' flag was recently removed by WT-8691. The test/format program (used by compatibility tests) may need an update to accommodate this change. 

            Assignee:
            Keith Bostic (Inactive)
            Reporter:
            Luke Chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: