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.

What does full compatibility in schema evolution ensure?

• Both backward and forward compatibility

• Neither backward nor forward compatibility

• Only forward compatibility

• Only backward compatibility

Which of the following is a limitation of full compatibility?

• It is less restrictive than backward compatibility

• It supports all types of field changes

• It restricts adding or deleting optional fields

• It allows adding mandatory fields

What is the purpose of full transitive compatibility?

• To ensure compatibility with all previously registered schemas

• To check compatibility with only the latest schema

• To allow adding mandatory fields

• To restrict schema changes to only optional fields

In the hands-on example, what is the new field added to the schema?

• nickname3

• nickname2

• nickname1

• nickname

What is the first step in updating the schema version in the example?

• Delete an optional field

• Add a mandatory field

• Update the consumer first

• Change the compatibility level to full

How is the schema version updated in the producer?

• By deleting an old field

• By adding a new field

• By changing the version in the Gradle file

• By updating the consumer

What indicates the successful completion of full compatibility implementation?

• The schema version remains unchanged

• The producer stops sending messages

• The schema version is updated and the consumer processes the new field

• The consumer fails to process the new field