Deleting a field without a default value in an Avro schema is which type of compatibility?

Deleting a field without a default value in an Avro schema is which type of compatibility?

• A. Backward
• B. Forward
• C. Full
• D. None

Answer: (A)

Backwards compatibility is at play here. When a field is removed from the schema and that field had no default value, the new schema no longer requires that data. Data written with the old schema still contains bytes for that field, but the newer reader simply doesn’t expect it and can ignore those bytes while decoding the rest of the record. In this sense, older data can be read by the newer schema without errors, which is what backward compatibility means. If you were thinking in the opposite direction (old readers reading data from a newer schema, or requiring the new field to exist), that would be forward or full compatibility.

Backwards compatibility is at play here. When a field is removed from the schema and that field had no default value, the new schema no longer requires that data. Data written with the old schema still contains bytes for that field, but the newer reader simply doesn’t expect it and can ignore those bytes while decoding the rest of the record. In this sense, older data can be read by the newer schema without errors, which is what backward compatibility means. If you were thinking in the opposite direction (old readers reading data from a newer schema, or requiring the new field to exist), that would be forward or full compatibility.