Kafka for Developers - Data Contracts Using Schema Registry - Adding a New Field in Schema - FORWARD Compatibility

The lecture covers forward compatibility in schema registries, explaining how new schema versions can be read by consumers using older schemas. It contrasts forward compatibility with backward compatibility and introduces forward transitive compatibility. The coding example involves updating a coffee order schema to include a new field, demonstrating how to handle compatibility issues and update schema versions effectively.

Which of the following is NOT a rule of forward compatibility?

• You can add new fields.

• You can delete optional fields.

• The consumer must upgrade first.

• The producer must upgrade first.

What is forward transitive compatibility?

• It checks compatibility with the next schema.

• It checks compatibility with only the last schema.

• It checks compatibility with all previously registered schemas.

• It does not check compatibility at all.

What is the main characteristic of forward compatibility in Schema Registry?

• Data produced with a new schema cannot be read by any consumers.

• Data produced with a new schema can only be read by consumers using the same schema.

• Data produced with an old schema can be read by consumers using the new schema.

• Data produced with a new schema can be read by consumers using the last schema.

In the practical implementation, what new field was added to the coffee order schema?

• Customer Name

• Pickup Type

• Order ID

• Order Date

What tool is used to update the build file to generate new Avro classes?

• Docker

• Jenkins

• Kubernetes

• Gradle or Maven

What issue arises if the compatibility type is set to backward when adding a new field?

• The producer stops working.

• The new field is ignored.

• The schema registration fails.

• The consumer crashes.

What happens when a consumer with an older schema version processes a record with a newer schema version?

• The consumer rejects the record.

• The consumer processes the record without the new fields.

• The consumer crashes.

• The consumer updates automatically.

Why is it important to upgrade the producer first in forward compatibility?

• To reduce processing time.

• To ensure new fields are available for consumers.

• To prevent data loss.

• To maintain backward compatibility.

What is the default compatibility type in Schema Registry?

• Backward

• Transitive

• Forward

• None

What is the benefit of using forward compatibility in a system with multiple consumers?

• It simplifies the producer's code.

• It reduces the number of schemas.

• New fields can be added without waiting for all consumers to update.

• All consumers must update simultaneously.