Stop persisting removed tiered keys in file metadata

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Configuration
    • None
    • Storage Engines - Persistence
    • 19.606
    • SE Persistence backlog
    • None

      Problem

      Removed tiered_storage / tiered_object keys still live on file_config / file_meta, so every new file metadata row would persist them. Those keys only need to remain on the create and connection-open APIs so leftover callers and WiredTiger.basecfg still parse. Stored file: metadata is not run through file.meta checks; getters ignore unknown keys.

      Change

      On tiered-depr (not develop — the keys are still live there):* Remove tiered_config from file_config and tiered_object from file_meta in dist/api_data.py.

      • Keep the keys on WT_SESSION.create and wiredtiger_open / reconfigure. Create already lists tiered_config separately.
      • Regenerate with dist/s_all.
      • Do not add a persist-time strip as the solution. Collapse from file_meta will stop writing the keys; leftover rows still open; a later alter drops them on rewrite.

      Test

      • New table/file create, checkpoint, reopen, and alter: metadata must not contain tiered_storage= or tiered_object=.
      • create(..., tiered_storage=(name=none)) still succeeds; name other than none is still ENOTSUP.
      • Leftover file: metadata that still contains the keys must still open.

            Assignee:
            Luke Pearson
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: