Kafka - Schema Registry
A new schema adds a required field without a default value. The registry rejects it. What is the likely reason?
A new schema adds a required field without a default value. The registry rejects it. What is the likely reason?
medium📝 Debug Q7 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand adding required fields without default
Adding a required field without default breaks backward compatibility because old data lacks that field.Step 2: Identify which compatibility rejects this
BACKWARD compatibility requires new schema to read old data, which fails here.Final Answer:
BACKWARD compatibility is enabled -> Option AQuick Check:
Adding required field without default breaks BACKWARD compatibility [OK]
Quick Trick: Adding required fields needs default for backward compatibility [OK]
Common Mistakes:
MISTAKES- Assuming FORWARD compatibility rejects this
- Thinking NONE compatibility rejects changes
- Ignoring default values for new required fields
Master "Schema Registry" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes