Kafka for Developers - Data Contracts Using Schema Registry - Deleting a Field in Schema - BACKWARD Compatibility

The lecture explains how to configure compatibility types in Schema Registry, focusing on backward compatibility. It covers the theory and practical aspects, including rules for schema evolution and application upgrades. The hands-on section demonstrates modifying schemas and ensuring compatibility between different versions, highlighting the benefits of Schema Registry in managing schema evolution.

What is the default compatibility level in Schema Registry?

• Forward

• None

• Backward

• Full

What does backward compatibility ensure in schema evolution?

• Only optional fields can be added

• Schemas cannot be changed once published

• Consumers can read data published with older schemas

• Producers can write data with new schemas only

Which fields can be modified under backward compatibility?

• No fields can be modified

• Only new fields can be added

• Fields can be deleted or optional fields added

• Mandatory fields can be added

In backward compatibility, which application should be upgraded first?

• Neither

• Producers

• Consumers

• Both simultaneously

What is the purpose of the value deserializer in backward compatibility?

• To serialize data

• To ensure data is encrypted

• To allow processing of new records with missing fields

• To compress data

What is the first step in the hands-on demonstration for backward compatibility?

• Delete the store field

• Add a new field

• Upgrade the producer

• Change the schema version to 1.0

What happens if a producer sends a message with a deleted field under backward compatibility?

• The consumer processes the message without the field

• The consumer throws an error

• The producer is forced to update

• The message is rejected

What is a key advantage of using backward compatibility?

• It allows schema evolution without synchronizing producer and consumer versions

• It requires all applications to be on the same schema version

• It prevents any schema changes

• It allows mandatory fields to be added

What should be done if a consumer needs to validate against all previous schemas?

• Use forward compatibility

• Use backward transmitter compatibility

• Use full compatibility

• Use backward compatibility

What is the recommended approach if you need to delete a field in a schema?

• Use backward compatibility

• Do not use Schema Registry

• Use full compatibility

• Use forward compatibility