The SQL Server connector supports blacklisting of specific columns now (DBZ-1067). That’s useful in cases where you’d like to exclude specific columns from emitted change data messages, e.g. to data protection considerations.

The "snapshot locking mode" option has been reworked (DBZ-947) and is named "snapshot isolation mode" now, better reflecting its semantics. A new mode "repeatable_read" has been added, and "none" has been renamed to "read_uncommitted". Please see the connector documentation and the migration notes for more details.

The connector allows for a much higher through-put now, thanks to caching of timestamps for the same LSN (DBZ-1078). Please refer to the change log for details on bugs fixed in this connector. A massive "Thank You" is in order to Grzegorz Kołakowski, for his tireless work on and testing of this connector!

Debezium’s embedded engine now comes with a new interface ChangeConsumer, which event handlers can implement if they’d like to process change events in bulks (DBZ-1080). That can result in substantial performance improvements when pushing change events to APIs that apply batch semantics themselves, such as the Kinesis Producer Library. You can learn more in the embedded engine docs.

All the relational connectors allow now to propagate the scale of numeric columns as a schema parameter (DBZ-1073). This is controlled via the column.propagate.source.type option and builds on the exposure of type name and width added in Debezium 0.8. All these schema parameters can be used when creating the schema of corresponding tables in sink databases.

Debezium’s container image for Apache Kafka allows to create and watch topics now (DBZ-1057). You also can specify a clean-up policy when creating a topic (DBZ-1038).

The Debezium MySQL connector handles unsigned SMALLINT columns as expected now. (DBZ-1063). For nullable columns with a default value, NULL values are correctly exported (DBZ-1064; previously, the default value would have been exported in that case).

The Postgres connector handles tables without a primary key correctly now (DBZ-1029). We’ve also applied a fix to make sure that the connector works with Postgres on Amazon RDS, which recently was broken due to an update of wal2json in RDS (DBZ-1083). Going forward, we’re planning to set-up CI jobs to test against Postgres on RDS in all the versions supported by the Debezium connector. This will help us to spot similar issues early on and react quickly.

Please see the change log for the complete list of all addressed issues.

This release wouldn’t have been possible without all the contributions by the following members of the Debezium community: Addison Higham, Amit Sela, Gagan Agrawal, Grzegorz Kołakowski, Ilia Bogdanov, Ivan Kovbas, Moira Tagle, Renato Mefi and Tony Rizko.

Thanks a lot!

The CR1 release took us a bit longer than anticipated. The release of Debezium 0.9.0.Final will therefore be moved to early February. Rather quickly thereafter we’re planning to release Debezium 0.9.1, which will provide improvements and potential bugfixes to the features added in 0.9.

For further plans beyond that, check out our road map. If you got any feedback or suggestions for future additions, please get in touch via the mailing list or in the comments below.