The different Debezium connectors provide great power and flexibility for setting up and running change data capture sources for a range of databases. But this flexibility also comes at a cost: getting started with the connectors can take some time for understanding all the different options and their semantics. Another critical aspect is operating the connectors, i.e. gaining insight into their current status and metrics, being able to react to connector failures, and more etc.

Based on this feedback from the community, we have explored over the last few months how a graphical user interface could help with these matters. The initial proof-of-concept looked very promising, so we decided to move forward and make the UI an official component of the Debezium project. Still under active development, you already can try out the UI today (available as a container image on Docker Hub) and use it to set up Debezium connectors in your Kafka Connect clusters.

We’ll follow up with more details on the Debezium UI in a separate blog post within the next few days, discussing its current status, the roadmap for this component, and more.

Continuing our current focus on the LogMiner-based CDC implementation for Oracle, we’ve fixed a substantial number of issues for this connector. Amongst them are:

Led by community member Kewei Shang, the Debezium connector for Vitess now supports Vitess 9.0 (DBZ-3100). The connector also can capture changes from JSON and ENUM columns (DBZ-3115, DBZ-3124), and it implements the configuration validation API of Kafka Connect (DBZ-3117).

Further fixes and improvements in this release including the following:

Altogether, a grand total of 78 issues have been addressed for this release.

As always, a big thanks you to all the community members who contributed: Adhaam Ehab, Ahmed Eljami, Bingqin Zhou, Fahim Farook, Ganesh Ramasubramanian, Harvey Yue, Kevin Pullin, Kewei Shang, Michael Cizmar, Nitin Agarwal, Russell Ballard, Shane Paul, Thomas Prelle, Thomas Thornton, and Yilong Chang.