Kafka for Developers - Data Contracts Using Schema Registry - Add/Delete Optional Fields - FULL Compatibility

The lecture explains full compatibility in schemas, which allows both backward and forward compatibility. It means old data can be read with a new schema and vice versa. The lecture provides a hands-on example of adding an optional field to a schema and updating the schema version. It also covers updating the producer and consumer to use the new schema version and changing the compatibility level. The lecture concludes with a discussion on schema versioning and the automatic increment of schema versions in the registry.

How does full transitive compatibility differ from full compatibility?

What happens when a new field is added in a schema with full compatibility?

What steps are involved in changing the compatibility level to full?