Debezium Blog

With Debezium 2.3, we introduced a preview of a brand new Debezium Operator with the aim to provide seamless deployment of Debezium Server to Kubernetes (k8s) clusters. The Debezium 2.4.0.Final release brings the next step towards the full support of this component. With this release, we are happy to announce that Debezium Operator is now available in the OperatorHub catalog for Kubernetes as well as in the community operator catalog embedded in the OpenShift and OKD distributions. The operator remains in the incubation phase; however, the full support of this component is approaching fast.

I’m pleased to announce the release of Debezium 1.4.1.Final!

We highly recommend upgrading from 1.4.0.Final and earlier versions as this release includes bug fixes and enhancements to several Debezium connectors which includes some of the following:

I am happy to announce the release of Debezium 1.2.1.Final!

This release includes several bug fixes to different Debezium connectors, and we highly recommend the upgrade from 1.2.0.Final and earlier versions:

  • The Debezium Postgres connector may have missed events from concurrent transactions when transitioning from snapshotting to streaming events from the WAL (DBZ-2288); this is fixed now when using the exported snapshotting mode; this mode should preferably be used, and for Debezium 1.3 we’re planning for this to be the basis for all the existing snapshotting modes

  • The Postgres JDBC driver got upgraded to 42.2.14 (DBZ-2317), which fixes a CVE in the driver related to processing XML column values sourced from untrusted XML input

  • The Debezium MySQL connector MariaDB’s supports ALTER TABLE statements with IF EXISTS (DBZ-2219); it also handles single dimension DECIMAL columns in CAST expressions (DBZ-2305)

  • The MySQL connector automatically filters out specific DML binlog entries from internal tables when using it with Amazon RDS (DBZ-2275)

  • The Debezium MongoDB connector got more resilient against connection losses (DBZ-2141)

I’m very happy to announce the release of Debezium 1.2.0.Final!

Over the last three months, the community has resolved nearly 200 issues. Key features of this release include:

  • New Kafka Connect single message transforms (SMTs) for content-based event routing and filtering; Upgrade to Apache Kafka 2.5

  • Schema change topics for the Debezium connectors for SQL Server, Db2 and Oracle

  • Support for SMTs and message converters in the Debezium embedded engine

  • Debezium Server, a brand-new runtime which allows to propagate data change events to a range of messaging infrastructures like Amazon Kinesis, Google Cloud Pub/Sub, and Apache Pulsar

  • A new column masking mode "consistent hashing", allowing to anonymize column values while still keeping them correlatable

  • New metrics for the MongoDB connector

  • Improved re-connect capability for the SQL Server connector

It’s my pleasure to announce the release of Debezium 1.2.0.CR1!

This release includes several notable features, enhancements, and fixes:

  • PostgreSQL can restrict the set of tables with a publication while using pgoutput (DBZ-1813).

  • Metrics MBean registration is skipped if a platform MBean server does not exist (DBZ-2089).

  • SQL Server reconnection improved during shutdown and connection resets (DBZ-2106).

  • EventRouter SMT can now pass non-String based keys (DBZ-2152).

  • PostgreSQL include.unknown.datatypes can now return strings rather than hashes (DBZ-1266).

  • Debezium Server now supports Google Cloud PubSub (DBZ-2092).

  • Debezium Server now supports Apache Pulsar sink (DBZ-2112).

You can find the complete list of addressed issues, upgrade procedures, and notes on any backward compatibility changes in the release notes.

I’m very happy to share the news that Debezium 1.2.0.Beta2 has been released!

Core feature of this release is Debezium Server, a dedicated stand-alone runtime for Debezium, opening up its open-source change data capture capabilities towards messaging infrastructure like Amazon Kinesis.

Overall, the community has fixed 25 issues since the Beta1 release, some of which we’re going to explore in more depth in the remainder of this post.