Question

A data engineering team ingests order events into Amazon MSK using Kafka Connect with a source connector, and serializes messages in Avro using AWS Glue Schema Registry. Downstream consumers include a long-running Flink application that cannot be redeployed frequently. Product teams will soon add several new optional fields to the order event schema. The team must ensure that existing consumers continue reading messages without deserialization failures after producers begin sending the new schema version. Which schema compatibility setting should the team configure in the Glue Schema Registry?

Accepted Answer

FORWARD compatibility, so consumers using an older schema can read data produced with the new schema

Answer

BACKWARD compatibility, so consumers using the new schema can read data produced with older schemas

Answer

NONE compatibility, so any schema change is accepted without validation

Answer

FULL_ALL compatibility, which requires renaming existing fields on each schema change