Kafka - Schema Registry
You try to register a new schema that removes a field, but the registry rejects it. What is the most likely cause?
You try to register a new schema that removes a field, but the registry rejects it. What is the most likely cause?
medium📝 Debug Q6 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand effect of removing fields on FULL compatibility
FULL compatibility requires both backward and forward compatibility, so removing fields breaks forward compatibility.Step 2: Identify which setting rejects the schema
Schema compatibility is set to FULL (FULL) rejects the schema because removing fields breaks forward compatibility.Final Answer:
Schema compatibility is set to FULL -> Option BQuick Check:
Removing fields rejected under FULL compatibility [OK]
Quick Trick: FULL compatibility rejects removing required fields [OK]
Common Mistakes:
MISTAKES- Thinking NONE rejects schemas
- Confusing BACKWARD and FORWARD effects
- Assuming registry always accepts schema changes
Master "Schema Registry" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes