Debezium Blog

Did you know January 16th is National Nothing Day? It’s the one day in the year without celebrating, observing or honoring anything.

Well, normally, that is. Because we couldn’t stop ourselves from sharing the news of the Debezium 1.1.0.Alpha1 release with you! It’s the first release after Debezium 1.0, and there are some really useful features coming with it. Let’s take a closer look.

Today it’s my great pleasure to announce the availability of Debezium 1.0.0.Final!

Since the initial commit in November 2015, the Debezium community has worked tirelessly to realize the vision of building a comprehensive open-source low-latency platform for change data capture (CDC) for a variety of databases.

Within those four years, Debezium’s feature set has grown tremendously: stable, highly configurable CDC connectors for MySQL, Postgres, MongoDB and SQL Server, incubating connectors for Apache Cassandra and Oracle, facilities for transforming and routing change data events, support for design patterns such as the outbox pattern and much more. A very active and welcoming community of users, contributors and committers has formed around the project. Debezium is deployed to production at lots of organizations from all kinds of industries, some with huge installations, using hundreds of connectors to stream data changes out of thousands of databases.

The 1.0 release marks an important milestone for the project: based on all the production feedback we got from the users of the 0.x versions, we figured it’s about time to express the maturity of the four stable connectors in the version number, too.

When a Debezium connector is deployed to a Kafka Connect instance it is sometimes necessary to keep database credentials hidden from other users of the Connect API.

Let’s remind how a connector registration request looks like for the MySQL Debezium connector:

Did you know December 12th is National Ding-a-Ling Day? It’s the day to call old friends you haven’t heard from in a while. So we thought we’d get in touch (not that is has been that long) with our friends, i.e. you, and share the news about the release of Debezium 1.0.0.CR1!

It’s the first, and ideally only, candidate release; so Debezium 1.0 should be out very soon. Quite a few nice features found their way into CR1:

While fall weather is in full swing, the Debezium community is not letting the unusually low, frigid temperatures get the best of us. It is my pleasure to announce the release of Debezium 1.0.0.Beta3!

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

  • Built against Kafka Connect 2.3.1 (DBZ-1612)

  • Renamed drop_on_stop configuration parameter to drop.on.stop (DBZ-1595)

  • Standardized source information for Cassandra connector (DBZ-1408)

  • Propagate MongoDB replicator exceptions so they are visible from Kafka Connect’s status endpoint (DBZ-1583)

  • Envelope methods should accept Instant rather than long values for timestamps (DBZ-1607)

  • Erroneously reporting no tables captured (DBZ-1519)

  • Avoid Oracle connector attempting to analyze tables (DBZ-1569)

  • Toasted columns should contain null in before rather than __debezium_unavailable_value (DBZ-1570)

  • Support PostgreSQL 11+ TRUNCATE operations using pgoutput decoder (DBZ-1576)

  • PostgreSQL connector times out in schema discovery for databases with many tables (DBZ-1579)

  • Value of ts_ms is not correct duing snapshot processing (DBZ-1588)

  • Heartbeats are not generated for non-whitelisted tables (DBZ-1592)

back to top