Featured Posts

Tags
analytics announcement announcement discussion survey apache kafka apache kafka apicurio avro aws batch caassandra camel cassandra cdc channels community community stories connectors containers cqrs custom datalake db2 ddd debezium debezium server debezium ui deduplication discussion docker elasticsearch event sourcing exactly once semantics example examples features fedora flink hiring ibmi iceberg images informix integration introduction jaeger jdbc json kafka kafka streams kafka streams kogito ksql kubernetes lakehouse machine learning mariadb metrics microservices mongo mongodb monitoring mysql news newsletter notifications online learning operator oracle outbox performance postgres presentation production quarkus questdb rds releases schema scylla secrets sentry serialization signaling smt snapshots spanner spark sql sqlserver tensorflow testcontainers tests time series timescaledb topics tracing transactions ui vagrant vitess website

We are very happy to announce the release of Debezium 1.7.0.CR2!

As we are moving ahead towards the final release we include mostly bugfixes. Yet this release contains important performance improvements and a new feature for read-only MySQL incremental snapshots.

Kafka based signalling

Recent releases provided a new feature for MySQL - incremental snapshotting from a read-only database. The snapshot process is based on GTIDs and does not need writing to signalling table. The problem is that triggering the process still required the existence and write access to the signalling table.

Now it is possible to send the signal via Kafka topic. This feature is available when the MySQL connector is configured with read-only = true. Please refer to the documentation for more details.

Performance improvements

Naveen Kumar identified multiple performance issues in the Debezium’s core critical path. He benchmarked them and provided pull requests solving them. If you are interested in details, please check DBZ-4015 and DBZ-3887.

Further Fixes

As we’re approaching the 1.7 Final release, most changes have been centered around bug fixing and maturing the codebase. Some of the resolved issues include:

  • Connection failure after snapshot wasn’t executed for a while (DBZ-3951)

  • Incorrect incremental snapshot DDL triggers snapshot that generates unending inserts against signalling table (DBZ-4013)

  • Several fixes to DML and DDL parsing for Oracle (DBZ-3917, DBZ-4017)

Altogether, 14 issues have been fixed for this release. A big thank you to all contributors: Anisha Mohanty, Bob Roldan, Chris Cranford, Gunnar Morling, Jiri Novotny, Jiri Pechanec, Katerina Galieva, Naveen Kumar KR, Robert Roldan, Vivek Wassan, and Xiao Fu.

We are on a good path towards 1.7.0.Final by the end of the next week.

Jiri Pechanec

Jiri is a software developer (and a former quality engineer) at Red Hat. He spent most of his career with Java and system integration projects and tasks. He lives near Brno, Czech Republic.

   

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.