I’m excited to announce the release of Debezium 1.9.6.Final!

This release focuses on bug fixes and stability; and is the recommended update for all users from earlier versions. This release contains 78 resolved issues overall.


A few noteworthy bug fixes and stability improvements include:

  • Oracle SCAN VIP support DBZ-3987

  • Memory leak in EventDeserializer caused by tableMapEventByTableId DBZ-5126

  • Postgres Incremental Snapshot on parent partitioned table not working DBZ-5240

  • Lob type data is inconsistent between source and sink, after modifying the primary key DBZ-5295

  • Unsigned tinyint conversion fails for MySQL 8.x DBZ-5343

  • NullPointerException thrown when unique index based on both system and non-system generated columns DBZ-5356

  • AWS DocumentDB (with MongoDB Compatibility) Connect Fail DBZ-5371

  • org.postgresql.util.PSQLException: Bad value for type timestamp/date/time: CURRENT_TIMESTAMP DBZ-5384

  • Timestamp with time zone column’s default values not in GMT DBZ-5403

  • OffsetStore not stopped if it fails to fully start DBZ-5433

  • Duplicate SCNs on same thread Oracle RAC mode incorrectly processed DBZ-5439

  • Outbox doesn’t check array consistecy properly when it detemines its schema DBZ-5475

  • Debezium connector task didn’t retry when failover in mongodb 5 DBZ-5479

  • Use TCCL as the default classloader to load interface implementations DBZ-5561

  • Vitess: Handle VStream close unepectedly DBZ-5579

  • Oracle connector parsing SELECT_LOB_LOCATOR event missing constant unavailable.value.placeholder DBZ-5581

  • Message with LSN foo larger than expected LSN bar DBZ-5597

  • Continuously WARNs about undo transactions when LOB is enabled DBZ-5635

  • Large numbers of ROLLBACK transactions can lead to memory leak when LOB is not enabled. DBZ-5645

In addition, there were quite a number of SQL parser fixes for both MySQL and Oracle, DBZ-5472, DBZ-5488, DBZ-5499, DBZ-5508, DBZ-5521, DBZ-5522, DBZ-5526, DBZ-5550, DBZ-5592, DBZ-5595, DBZ-5605, DBZ-5630, and DBZ-5643.

Please refer to the release notes to learn more about all fixed bugs, update procedures, etc.

Outlook, What’s next?

Debezium 1.9 will continue to receive bug fix and maintenance changes throughout the early part of the next quarter. I expect there to be at least a 1.9.7.Final in the middle to late October timeframe, potentially wrapping up the 1.9 release stream.

Debezium 2.0 is wrapping up with the latest 2.0.0.Beta2 build released just last week. We are currently focusing on bug fixes, stability, and polishing the Debezium 2.0 release stream. We expect to have 2.0.0.CR1 released in about another week or so with 2.0.0.Final scheduled for mid-October.

Until next time, keep an eye out as we’ll soon be discussing what’s to come in Debezium 2.1 later this year!

Chris Cranford

Chris is a software engineer at Red Hat. He previously was a member of the Hibernate ORM team and now works on Debezium. He lives in North Carolina just a few hours from Red Hat towers.


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 Zulip, 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.