Subscribe


Debezium 0.10.0.Beta1 Released

Another week, another Debezium release — I’m happy to announce the release of Debezium 0.10.0.Beta1!

Besides the upgrade to Apache Kafka 2.2.1 (DBZ-1316), this mostly fixes some bugs, including a regression to the MongoDB connector introduced in the Alpha2 release (DBZ-1317).

A very welcomed usability improvement is that the connectors will log a warning now if not at least one table is actually captured as per the whitelist/blacklist configuration (DBZ-1242). This helps to prevent the accidental exclusion all tables by means of an incorrect filter expression, in which case the connectors "work as intended", but no events are propagated to the message broker.

Please see the release notes for the complete list of issues fixed in this release. Also make sure to examine the upgrade guidelines for 0.10.0.Alpha1 and Alpha2 when upgrading from earlier versions.

Many thanks to community members Cheng Pan and Ching Tsai for their contributions to this release!

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Gitter, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.


Debezium 0.10.0.Alpha2 Released

Release early, release often — Less than a week since the Alpha1 we are announcing the release of Debezium 0.10.0.Alpha2!

This is an incremental release that completes some of the tasks started in the Alpha1 release and provides a few bugfixes and also quality improvements in our Docker images.

The change in the logic of the snapshot field has been delivered (DBZ-1295) as outlined in the last announcement. All connectors now provide information which of the records is the last one in the snapshot phase so that downstream consumers can react to this.

Apache ZooKeeper was upgraded to version 3.4.14 to fix a security vulnerability (CVE-2019-0201).

Our regular contributor Renato dived deeply into our image build scripts and enriched (DBZ-1279) them with a Dockerfile linter.

Schema change events include the table name(s) in the metadata describing which tables are affected by the change (DBZ-871).

Bartosz Miedlar has fixed a bug in MySQL ANTLR grammar causing issues with identifiers in backquotes (DBZ-1300).

What’s next?

We hope we will be able to keep the recent release cadence and get lout the first beta version of 0.10 in two weeks.

Stay tuned for more!

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Gitter, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.


Debezium 0.10.0.Alpha1 "Spring Clean-Up" Edition Released

I’m very happy to announce the release of Debezium 0.10.0.Alpha1!

The major theme for Debezium 0.10 will be to do some clean-up (that’s what you do at this time of the year, right?); we’ve planned to remove a few deprecated features and to streamline some details in the structure the CDC events produced by the different Debezium connectors.

This means that upgrading to Debezium 0.10 from earlier versions might take a bit more planning and consideration compared to earlier upgrades, depending on your usage of features and options already marked as deprecated in 0.9 and before. But no worries, we’re describing all changes in great detail in this blog post and the release notes.

Why?

First of all, let’s discuss a bit why we’re doing these changes.

Over the last three years, Debezium has grown from supporting just a single database into an entire family of CDC connectors for a range of different relational databases and MongoDB, as well as accompanying components such as message transformations for topic routing or implementing the outbox pattern.

As in any mature project, over time we figured that a few things should be done differently in the code base than we had thought at first. For instance we moved from a hand-written parser for processing MySQL DDL statements to a much more robust implementation based on Antlr. Also we realized the way certain temporal column types were exported was at risk of value overflow in certain conditions, so we added a new mode not prone to these issues. As a last example, we made options like the batch size used during snapshotting consistent across the different connectors.

Luckily, Debezium quickly gained traction and despite the 0.x version number, it is used heavily in production at a large number of organizations, and users rely on its stability. So whenever we did such changes, we aimed at making the upgrade experience as smooth as possible; usually that means that the previous behavior is still available but is marked as deprecated in the documentation, while a new improved option, implementation etc. is added and made the default behavior.

At the same time we realized that there are a couple of differences between the connectors which shouldn’t really be there. Specifically, the source block of change events has some differences which make a uniform handling by consumers more complex than it should be; for instance the timestamp field is named "ts_sec" in MySQL events but "ts_usec" for Postgres.

With all this in mind, we decided that it is about time to clean up these issues. This done for a couple of purposes:

  • Keeping the code base maintainable and open for future development by removing legacy code such as deprecated options and their handling as well as the legacy MySQL DDL parser

  • Making CDC events from different connectors easier to consume by unifying the source block created by the different connectors as far as possible

  • Preparing the project to go to version 1.0 with an even stronger promise of retaining backwards compatibility than already practiced today

What?

Now as we have discussed why we feel it’s time for some "clean-up", let’s take a closer look at the most relevant changes. Please also refer to the "breaking changes" section of the migration notes for more details.

  • The legacy DDL parser for MySQL has been removed (DBZ-736); if you are not using the Antlr-based one yet (it was introduced in 0.8 and became the default in 0.9), it’s highly recommended that you test it with your databases. Should you run into any parsing errors, please report them so we can fix them for the 0.10 Final release.

  • The SMTs for retrieving the new record/document state from change events have been renamed from io.debezium.transforms.UnwrapFromEnvelope and io.debezium.connector.mongodb.transforms.UnwrapFromMongoDbEnvelope into ExtractNewRecordState and ExtractNewDocumentState, respectively (DBZ-677). The old names can still be used as of 0.10, but doing so will raise a warning. They are planned for removal in Debezium 0.11.

  • Several connector options that were deprecated in earlier Debezium versions have been removed (DBZ-1234): the drop.deletes option of new record/document state extraction SMTs (superseded by delete.handling.mode option), the rows.fetch.size option (superseded by snapshot.fetch.size), the adaptive value of time.precision.mode option for MySQL (prone to value loss, use adaptive_microseconds instead) and the snapshot.minimal.locks for the MySQL connector (superseded by snapshot.locking.mode)

  • Several option names of the (incubating) SMT for the outbox pattern have been renamed for the sake of consistency (DBZ-1289)

  • Several fields within the source block of CDC events have been renamed for the sake of consistency (DBZ-596); as this is technically a backwards-incompatible change when using Avro and the schema registry, we’ve added a connector option source.struct.version which, when set to the value v1, will have connectors produce the previous source structure. v2 is the default and any consumers should be adjusted to work with the new source structure as soon as possible.

New Features and Bugfixes

Besides these changes, the 0.10.0.Alpha1 release also contains some feature additions and bug fixes:

  • The SQL Server connector supports custom SELECT statements for snapshotting (DBZ-1224)

  • database, schema and table/collection names have been added consistently to the source block for CDC events from all connectors (DBZ-875)

  • Client authentication works for the MySQL connector(DBZ-1228)

  • The embedded engine doesn’t duplicate events after restarts any longer (DBZ-1276)

  • A parser bug related to CREATE INDEX statements was fixed (DBZ-1264)

Overall, 30 issues were addressed in this release. Many thanks to Arkoprabho Chakraborti, Ram Satish and Yuchao Wang for their contributions to this release!

Speaking of contributors, we did some housekeeping to the list of everyone ever contributing to Debezium, too. Not less than exactly 111 individuals have contributed code up to this point, which is just phenomenal! Thank you so much everyone, you folks rock!

Outlook

Going forward, there are some more details we’d like to unify across the different connectors before going to Debezium 0.10 Final. For instance the source attribute snapshot will be changed so it can take one of three states: true, false or last (indicating that this event is the last one created during initial snapshotting).

We’ll also continue our efforts to to migrate the existing Postgres connector to the framework classes established for the SQL Server and Oracle connectors. Another thing we’re actively exploring is how the Postgres could take advantage of the "logical replication" feature added in Postgres 10. This may provide us with a way to ingest change events without requiring a custom server-side logical decoding plug-in, which proves challenging in cloud environments where there’s typically just a limited set of logical decoding options available.

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Gitter, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.


Debezium 0.9.5.Final Released

It’s my pleasure to announce the release of Debezium 0.9.5.Final!

This is a recommended update for all users of earlier versions; besides bug fixes also a few new features are provide. The release contains 18 resolved issues overall.

Apache Kafka Update and New Features

This release has been built against and tested with Apache Kafka 2.2.0 (DBZ-1227). Earlier versions are continued to be supported as well.

For all the connectors it is possible now to specify the batch size when taking snapshots (DBZ-1247). The new connector option snapshot.fetch.size has been introduced for that. This option replaces the earlier option rows.fetch.size which existed in some of the connectors and which will be removed in Debezium 0.10. Existing connector instances should therefore be re-configured to use the new option.

Continuing the work from Debezium 0.9.4, the Postgres connector supports some more column types: MACADDR and MACADDR8 (DBZ-1193) as well as INT4RANGE, INT8RANGE and NUMRANGE (DBZ-1076).

Fixes

Amongst others, this release includes the following fixes:

  • Failing to specify value for database.server.name results in invalid Kafka topic name (DBZ-212)

  • Postgres Connector times out in schema discovery for DBs with many tables (DBZ-1214)

  • Oracle connector: JDBC transaction can only capture single DML record (DBZ-1223)

  • Lost precision for timestamp with timezone (DBZ-1236)

  • NullpointerException due to optional value for commitTime (DBZ-1241)

  • Default value for datetime(0) is incorrectly handled (DBZ-1243)

  • Microsecond precision is lost when reading timetz data from Postgres (DBZ-1260)

Please refer to the release notes for the complete list of issues fixed in Debezium 0.9.5.

We’re very thankful to the following community members who contributed to this release: Addison Higham, Andrey Pustovetov, Jork Zijlstra, Krizhan Mariampillai, Mathieu Rozieres and Shubham Rawat.

Outlook

This release is planned to be the last in the 0.9 line.

We’re now going to focus on Debezium 0.10, whose main topic will be to clean up a few things: we’d like to remove a few deprecated options and features (e.g. the legacy DDL parser in the MySQL connector). We’re also planning to do a thorough review of the event structure of the different connectors; for instance in the source block of CDC messages there are a some field names that should be unified. We believe users will benefit from a more consistent experience across the connectors.

Another focus area will be to migrate the existing Postgres connector to the framework classes established for the SQL Server and Oracle connectors. This will allow to expose some new features for the Postgres connector, e.g. the monitoring capabilities already rolled out for the other two connectors.

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Gitter, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.


Debezium 0.9.4.Final Released

It’s my pleasure to announce the release of Debezium 0.9.4.Final!

This is a drop-in replacement for earlier Debezium 0.9.x versions, containing mostly bug fixes and some improvements related to metrics. Overall, 17 issues were resolved.

MySQL Connector Improvements

The Debezium connector for MySQL comes with two new metrics:

  • Whether GTID is enabled for offset tracking or not (DBZ-1221)

  • Number of filtered events (DBZ-1206)

It also supports database connections using TLS 1.2 (DBZ-1208) now.

New Postgres Datatypes

The Postgres connector now allows to capture changes to columns of the CIDR and INET types (DBZ-1189).

Bug Fixes

The fixed bugs include the following:

  • Closing connection after snapshotting (DBZ-1218)

  • Can parse ALTER statement affecting enum column with character set options (DBZ-1203)

  • Avoiding timeout after bootstrapping a new table (DBZ-1207)

Check out the release notes for the complete list of issues fixed in Debezium 0.9.4.

Many thanks to Debezium community members Andrey Pustovetov, Jordan Bragg, Joy Gao, Preethi Sadagopan, Renato Mefi, Sasha Kovryga, Shubham Rawat and Stephen Powis for their contributions to this release!

About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Gitter, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.


back to top