From 946116dfef481d723aebc70a66ca06af486609a6 Mon Sep 17 00:00:00 2001 From: Jiri Pechanec Date: Thu, 21 Sep 2023 07:47:20 +0200 Subject: [PATCH] [release] Changelog for 2.3.4.Final --- _data/releases/2.3/2.3.4.Final.yml | 5 +++ releases/2.3/release-notes.asciidoc | 52 +++++++++++++++++++++++++++++ 2 files changed, 57 insertions(+) create mode 100644 _data/releases/2.3/2.3.4.Final.yml diff --git a/_data/releases/2.3/2.3.4.Final.yml b/_data/releases/2.3/2.3.4.Final.yml new file mode 100644 index 00000000000..c3f66273d1e --- /dev/null +++ b/_data/releases/2.3/2.3.4.Final.yml @@ -0,0 +1,5 @@ +date: 2023-09-21 +version: "2.3.4.Final" +stable: true +summary: MongoDB improvements for handling oversized documents +#announcement_url: diff --git a/releases/2.3/release-notes.asciidoc b/releases/2.3/release-notes.asciidoc index 0a43cc5b35d..aa69245a515 100644 --- a/releases/2.3/release-notes.asciidoc +++ b/releases/2.3/release-notes.asciidoc @@ -15,6 +15,58 @@ Release numbers follow http://semver.org[Semantic Versioning]. toc::[] +[[release-2.3.4-final]] +== *Release 2.3.4.Final* _(September 21st 2023)_ + +See the https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12317320&version=12412661[complete list of issues]. + +=== Kafka compatibility + +This release has been built against Kafka Connect 3.4.0 and has been tested with version 3.4.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.3.4.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.3.4.Final plugin files, and restart the connector using the same configuration. +Upon restart, the 2.3.4.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://hub.docker.com/u/debezium[DockerHub]. + + +=== Breaking changes + +There are no breaking changes in this release. + + +=== New features + +* Configurable order of user defined and internal aggregation pipeline https://issues.redhat.com/browse/DBZ-6872[DBZ-6872] + + +=== Fixes + +* MongoDB New Document State Extraction: original name overriding does not work https://issues.redhat.com/browse/DBZ-6773[DBZ-6773] +* errors.max.retries = 0 Causes retrievable error to be ignored https://issues.redhat.com/browse/DBZ-6866[DBZ-6866] +* Oracle alter table drop constraint fails when cascading index https://issues.redhat.com/browse/DBZ-6876[DBZ-6876] +* ExtractNewRecordState's schema cache is not updated with arrival of the ddl change event https://issues.redhat.com/browse/DBZ-6901[DBZ-6901] +* Clean log printout in Redis Debezium Sink https://issues.redhat.com/browse/DBZ-6908[DBZ-6908] +* MySql connector get NPE when snapshot.mode is set to never and signal data collection configured https://issues.redhat.com/browse/DBZ-6937[DBZ-6937] +* Sanity check / retry for redo logs does not work per Oracle RAC thread https://issues.redhat.com/browse/DBZ-6938[DBZ-6938] + + +=== Other changes + +* Increase Oracle log level to DEBUG for several key important log messages https://issues.redhat.com/browse/DBZ-6880[DBZ-6880] +* Document cursor pipeline ordering and oversize document handling mode https://issues.redhat.com/browse/DBZ-6883[DBZ-6883] + + + [[release-2.3.3-final]] == *Release 2.3.3.Final* _(September 4th 2023)_