Kafka - Schema Registry
Which of the following is a valid way to add a new optional field in an Avro schema to maintain forward compatibility?
Which of the following is a valid way to add a new optional field in an Avro schema to maintain forward compatibility?
easy📝 Syntax Q3 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand forward compatibility for adding fields
Adding a new optional field requires a default value to keep old data readable.Step 2: Check options for default value
Only "newField": {"type": "string", "default": ""} includes a default value for the new field, making it forward compatible.Final Answer:
"newField": {"type": "string", "default": ""} -> Option AQuick Check:
Forward compatible new field needs default value [OK]
Quick Trick: Add default value to new field for forward compatibility [OK]
Common Mistakes:
MISTAKES- Adding fields without default values
- Confusing optional with required fields
- Using wrong syntax for default
Master "Schema Registry" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes