Schema mismatch: expected field X of type Y, found Z after LinkedIn online DDL rollback
Schema mismatch after LinkedIn online DDL rollback The goal is to guarantee that a rollback of an online DDL schema change does not leave consumers deserializing data with the newer Avro schema, which currently produces errors such as “Schema mismatch: expected field X of type Y, found Z”. LinkedIn’s internal online DDL tool applies changes incrementally but
linkedin