The metadata should not imply that an empty value is true

XMLWordPrintableJSON

    • None
    • None

      The current format of the metadata uses an empty boolean value to mean true. That allows for a minor space saving, but results in confusion when reviewing the content of configuration strings.

      We should store an explicit true value in the metadata, and do it in such a way that it's backward compatible. An example of where this is confusing is when looking at the wt list -v output from a table with cache_resident set to true:

      allocation_size=4KB,app_metadata=,block_allocation=best,block_compressor=,cache_resident=,checkpoint=...
      

              Assignee:
              Keith Bostic (Inactive)
              Reporter:
              Alexander Gorrod
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: