schema evolution
Change a stored format while handling older data deliberately.
Use this when An app update makes existing drafts or settings unreadable.
without the term
“After the last update, people's old saved settings don't load anymore because we renamed some fields. Can you make old saved data still work and upgrade it safely?”
with the term · How do you ask a model for schema evolution?
Add schema evolution for this stored draft. Migrate a previous-version fixture and verify that its content survives the upgrade.
What is schema evolution?
Schema evolution defines how readers and writers handle multiple versions of a data format.
Why does schema evolution matter when vibe coding?
New generated fields can silently change assumptions about files already on disk.
How do you do schema evolution?
Version the format and define the old-data path. Check a previous-version fixture without losing the original.
What goes wrong with schema evolution?
A failed migration overwrites the only copy of the old data.
Sources for this entry
- Confluent: Schema evolution and compatibility
Schema Registry versions schemas and enforces configured compatibility modes; backward and forward compatibility differ.
Sources checked . Source checks do not establish human editorial approval. How we check content.