compatibility level
A schema registry setting per subject that decides which schema changes are allowed: BACKWARD, FORWARD, FULL or NONE.
In more detail
The registry rejects a new version that breaks the rule before any producer can use it. BACKWARD is the usual default, and the transitive variants check against every earlier version instead of only the latest.
Related terms
- backward compatibility — The property that a new version of an interface still works for clients written against the old one.
- forward compatibility — A schema change is forward compatible when consumers still using the old schema can read data written with the new one.
- FULL compatibility — The compatibility level that requires schema changes to be both backward and forward compatible.
- NONE compatibility — The compatibility level that turns checking off, so the schema registry accepts any change.
- 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
- Compatibility Modes — Apache Kafka & Event Streaming