Kafka - Schema Registry
A new schema changes a field type from
int to string without default. What is the compatibility status?A new schema changes a field type from int to string without default. What is the compatibility status?
medium📝 Debug Q7 of Q15
Step-by-Step Solution
Solution:
Step 1: Analyze type change impact
Changing field type from int to string breaks both backward and forward compatibility.Step 2: Confirm no default value
Without default, old data can't be read by new schema and vice versa.Final Answer:
Not compatible -> Option CQuick Check:
Type change without default breaks all compatibility [OK]
Quick Trick: Type changes without default break compatibility [OK]
Common Mistakes:
MISTAKES- Assuming backward compatibility
- Ignoring type changes
- Thinking default is optional here
Master "Schema Registry" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes