Loading...

XML

Word

Printable

JSON

Epic Link:
Ensure that all disagg data formats are extensible
Assigned Teams:

Storage Engines - Persistence
Sprint:
SE Persistence - 2026-02-13, SE Persistence - 2026-02-27, SE Persistence - 2026-03-13, SE Persistence - 2026-03-27
Story Points:
None

We need to redesign the shared turtle data format. We need to think about:

What should be included in the data? Version information for upgrade/downgrade, checkpoint information, global timestamps, and etc.
What data format we should use?
What kind of testing we should do?

depends on

WT-16252 Preserve the largest allocated table_id in the checkpoint metadata

is blocked by

WT-16875 Relax turtle metadata parsing to ignore unknown fields

is related to

WT-16055 Implement KEK read path mechanism

WT-15984 Add version numbers to "checkpoint_meta"

related to

WT-16875 Relax turtle metadata parsing to ignore unknown fields