Quite a few of us are looking at using the Confluent stack with their Avro schema registry as a way to serialize Debezium data. The schema registry prevents backwards incompatible schema changes on the Avro messages that flow through it (rightfully so).

This presents a problem. A DB admin (or someone else) might make a DB schema change that results in backwards incompatible messages flowing through the system (e.g. changing column types, or deleting a column).

There's currently no way for us to easily determine if a DB schema change is going to break Debezium's message compatibility. Although this appears to be a problem related to the schema registry tool, I'd argue that preventing backwards compatible changes is generally a good thing and worth doing, independent of whether the Confluent stack is used or not.

It would be nice if Debezium provided some tool that would allow us to validate our DDLs are backwards compatible before we run them on our DB tables.