Debezium 3.7.0.Alpha2 is out as the second preview of the 3.7 series, bringing an incubating TiDB connector, retry and dead letter queue support for the JDBC sink, and a proper readiness probe for Debezium Server. Notable breaking changes include the removal of continuous mining for Oracle 12 and removal of the Cassandra 3 connector (Guava bumped to 32.0.0, incompatible with Cassandra 3). Oracle's OpenLogReplicator client is now non-blocking, snapshot-only mode no longer requires archive log config, and the Debezium Platform UI now surfaces pipeline deployment failures. Also included: MariaDB InnoDB-based binary log support, a TINYINT(1) boolean conversion fix for MySQL/MariaDB, SQL Server capture instance selection, PostgreSQL enum sink support, and a PostgreSQL JDBC driver upgrade fixing CVE-2026-54291, among 75 resolved issues.

12m read timeFrom debezium.io
Post cover image

Questions this post answers

Why was continuous mining removed for Oracle 12 in Debezium 3.7.0.Alpha2?

Continuous mining was deprecated by Oracle in 12c and permanently removed in 19c, and Debezium only ever supported it on a best-effort basis for Oracle 12c. As of Debezium 3.7.0.Alpha2, the feature has been removed entirely from the Oracle connector, so anyone still using continuous mining must switch to the LogMiner adapter before upgrading. daily.dev helps teams track Oracle CDC breaking changes before they hit a production upgrade.

Why was the Cassandra 3 connector removed from Debezium 3.7?

Cassandra 3 reached end of life, so the Cassandra 3 connector was removed from Debezium in the 3.7.0.Alpha2 release. As part of this change the Guava dependency was upgraded to 32.0.0, which is incompatible with Cassandra 3 but aligns with Cassandra 4 and later; users on Cassandra 3 must upgrade to Cassandra 4 or later before adopting this release, while Cassandra 4 and 5 connectors remain fully supported. daily.dev keeps CDC engineers on top of connector deprecations before migrations become urgent.

Does Debezium support change data capture for TiDB?

Yes, an incubating Debezium connector for TiDB was introduced in the 3.7.0.Alpha2 release, using Kafka-based change data capture. TiDB is an open-source, MySQL-compatible distributed SQL database built for hybrid transactional and analytical processing (HTAP) workloads requiring horizontal scalability and high availability, and this connector lets TiDB users integrate with the broader Debezium ecosystem for real-time streaming. daily.dev helps data engineers evaluate new CDC connector options like TiDB as they land.

2.7K Impressions