From 7b4fbdb876b44ace56f5f0e84e1df444aff0c633 Mon Sep 17 00:00:00 2001 From: Jiri Pechanec Date: Thu, 30 May 2024 11:14:07 +0200 Subject: [PATCH] [release] Changelog for 2.6.2.Final --- _data/releases/2.6/2.6.2.Final.yml | 5 +++ releases/2.6/release-notes.asciidoc | 62 +++++++++++++++++++++++++++++ 2 files changed, 67 insertions(+) create mode 100644 _data/releases/2.6/2.6.2.Final.yml diff --git a/_data/releases/2.6/2.6.2.Final.yml b/_data/releases/2.6/2.6.2.Final.yml new file mode 100644 index 00000000000..86d9963881a --- /dev/null +++ b/_data/releases/2.6/2.6.2.Final.yml @@ -0,0 +1,5 @@ +date: 2024-05-30 +version: "2.6.2.Final" +stable: true +summary: Better Oracle connector performance for large number of tables; Fixed race condition in PostgreSQL on offset flushing; Fixed Avro compatibility issues during upgrde to 2.6; Removed excessive logging +# announcement_url: diff --git a/releases/2.6/release-notes.asciidoc b/releases/2.6/release-notes.asciidoc index f74383aa7ae..f2dbe9daaed 100644 --- a/releases/2.6/release-notes.asciidoc +++ b/releases/2.6/release-notes.asciidoc @@ -15,6 +15,68 @@ Release numbers follow http://semver.org[Semantic Versioning]. toc::[] +[[release-2.6.2-final]] +== *Release 2.6.2.Final* _(May 30th 2024)_ + +See the https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12317320&version=12425583[complete list of issues]. + +=== Kafka compatibility + +This release has been built against Kafka Connect 3.7.0 and has been tested with version 3.7.0 of the Kafka brokers. +See the https://kafka.apache.org/documentation/#upgrade[Kafka documentation] for compatibility with other versions of Kafka brokers. + + +=== Upgrading + +Before upgrading any connector, be sure to check the backward-incompatible changes that have been made since the release you were using. + +When you decide to upgrade one of these connectors to 2.6.2.Final from any earlier versions, +first check the migration notes for the version you're using. +Gracefully stop the running connector, remove the old plugin files, install the 2.6.2.Final plugin files, and restart the connector using the same configuration. +Upon restart, the 2.6.2.Final connectors will continue where the previous connector left off. +As one might expect, all change events previously written to Kafka by the old connector will not be modified. + +If you are using our container images, then please do not forget to pull them fresh from https://quay.io/organization/debezium[Quay.io]. + + +=== Breaking changes + +There are no breaking changes in this release. + + +=== New features + +* Debezium oracle connectors needs to support IN clause for log miner query for more than 1000 tables as it creates performance issue https://issues.redhat.com/browse/DBZ-7847[DBZ-7847] + + +=== Fixes + +* After the initial deployment of Debezium, if a new table is added to MSSQL, its schema is was captured https://issues.redhat.com/browse/DBZ-7697[DBZ-7697] +* NO_DATA snapshot mode validation throw DebeziumException on restarts if snapshot is not completed https://issues.redhat.com/browse/DBZ-7780[DBZ-7780] +* DDL statement couldn't be parsed https://issues.redhat.com/browse/DBZ-7788[DBZ-7788] +* old class reference in ibmi-connector services https://issues.redhat.com/browse/DBZ-7795[DBZ-7795] +* Ad-hoc blocking snapshot not working through file channeling without inserting a row in the database. https://issues.redhat.com/browse/DBZ-7806[DBZ-7806] +* Postgres: Potential data loss on connector restart https://issues.redhat.com/browse/DBZ-7816[DBZ-7816] +* Sql Server incorrectly applying quoted snapshot statement overrides https://issues.redhat.com/browse/DBZ-7828[DBZ-7828] +* Debezium JDBC Sink not handle order correctly https://issues.redhat.com/browse/DBZ-7830[DBZ-7830] +* Debezium MySQL Snapshot Connector Fails https://issues.redhat.com/browse/DBZ-7858[DBZ-7858] +* Support Oracle DDL Alter Audit Policy https://issues.redhat.com/browse/DBZ-7864[DBZ-7864] +* Support Oracle DDL Create Audit Policy https://issues.redhat.com/browse/DBZ-7865[DBZ-7865] +* Default value of error retries not interpreted correctly https://issues.redhat.com/browse/DBZ-7870[DBZ-7870] +* Avro schema compatibility issues when upgrading from Oracle Debezium 2.5.3.Final to 2.6.1.Final https://issues.redhat.com/browse/DBZ-7880[DBZ-7880] +* ParsingException (MySQL 8): create trigger if exists https://issues.redhat.com/browse/DBZ-7881[DBZ-7881] +* Debezium can't handle columns with # in its name https://issues.redhat.com/browse/DBZ-7893[DBZ-7893] +* Oracle interval default values are not properly parsed https://issues.redhat.com/browse/DBZ-7898[DBZ-7898] + + +=== Other changes + +* Add c3p0 timeout configuration example to JDBC sink https://issues.redhat.com/browse/DBZ-7822[DBZ-7822] +* in the Cassandra documentation, there is a typo which should have been disable not Dusable. https://issues.redhat.com/browse/DBZ-7851[DBZ-7851] +* Too much logs after Debezium update https://issues.redhat.com/browse/DBZ-7871[DBZ-7871] + + + [[release-2.6.1-final]] == *Release 2.6.1.Final* _(April 12nd 2024)_