forward compatibility
A schema change is forward compatible when consumers still using the old schema can read data written with the new one.
In more detail
Adding a field or removing an optional one is forward compatible, because old readers ignore what they do not know. Under FORWARD you upgrade producers first, then consumers.
Related terms
- compatibility level — A schema registry setting per subject that decides which schema changes are allowed: BACKWARD, FORWARD, FULL or NONE.
- backward compatibility — The property that a new version of an interface still works for clients written against the old one.
- schema evolution — Changing the structure of your data over time while keeping existing producers and consumers working.
Taught in
- The Field The Registry Refused — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Seventy One Percent — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Compatibility Modes — Apache Kafka & Event Streaming