schema evolution
Changing the structure of your data over time while keeping existing producers and consumers working.
In more detail
Safe changes include adding optional fields with defaults; unsafe ones include renaming, removing required fields and changing types. A schema registry's compatibility level enforces which changes are allowed.
Related terms
- compatibility level — A schema registry setting per subject that decides which schema changes are allowed: BACKWARD, FORWARD, FULL or NONE.
- breaking change — A change that makes existing users of a program or interface stop working until they change something too.
- optional field — A field that may be missing from a record, which readers must handle, typically by using a default value.
- expand-and-contract — A way to change a live database in safe steps: add the new structure, move data and code to it, then remove the old structure.
Taught in
- The Field The Registry Refused — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Compatibility Modes — Apache Kafka & Event Streaming
- Evolving An Event Without Breaking Consumers — Apache Kafka & Event Streaming