optional field
A field that may be missing from a record, which readers must handle, typically by using a default value.
In more detail
Adding an optional field is the safest schema change, since old consumers ignore it and new consumers can fall back to a default when it is absent. A required field must always be present.
Example
v.get('currency', 'USD')Related terms
- schema evolution — Changing the structure of your data over time while keeping existing producers and consumers working.
- JSON Schema — A standard vocabulary for describing the allowed shape of JSON data: which fields exist, their types, which are required and what values are allowed.
- backward compatibility — The property that a new version of an interface still works for clients written against the old one.
Taught in
- The Retry That Overtook — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Field The Registry Refused — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Twelve Lines Instead Of Four Hundred — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Setting That Came Back — 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