Kafka for Developers - Data Contracts Using Schema Registry - Modify Field Names - NONE Compatibility

The lecture covers None compatibility in schema checks, explaining when to use it, such as changing field types or names. It emphasizes creating new topics and schemas to avoid handling incompatible schemas. A practical example demonstrates changing a schema field name and updating versions. The lecture concludes with testing the changes and ensuring compatibility.

What does 'None compatibility' mean in the context of schema compatibility?

In what scenarios is it recommended to use 'None compatibility'?

What is the main reasoning behind creating a new topic and schema when changing field types?

What steps are involved in changing a field name from 'name' to 'full name' in the schema?

What should be done if a consumer receives an error due to an invalid field name?

How does changing the compatibility type to 'None' affect message publishing?

What is the significance of the schema version change from 5.0 to 6.0 in the context of non-compatibility?