2.5.0.Final announcement

_posts/2023-12-20-debezium-2-5-final-released.adoc → _posts/2023-12-21-debezium-2-5-final-released.adoc

@@ -1,7 +1,7 @@
 ---
 layout: post
 title:  Debezium 2.5.0.Final Released
-date:   2023-12-19
+date:   2023-12-21
 tags: [ releases, mongodb, mysql, postgres, sqlserver, cassandra, oracle, db2, vitess, outbox, spanner, jdbc ]
 author: mfvitale
 ---
@@ -34,17 +34,10 @@ MongoDB::
 Unfortunately, while we understand that users may have taken advantage of this behavior, it was unintended and not supported.
 Debezium 2.5 removes this ability entirely, and it's a step in the forward goal to deprecate and remove the replica-set streaming mode in MongoDB completely (https://issues.redhat.com/browse/DBZ-7139[DBZ-7139]).
 
-* The upgrade to Debezium 2.5 brings a change to MongoDB's default implementation.
-In previous builds, the default connection mode was `replica_set`; however with Debezium 2.5 this is now `sharded`.
-If you were connecting to a sharded cluster and not explicitly setting a connection mode; ergo, relying on the default behavior, you must review your connector configuration and make adjustments. (https://issues.redhat.com/browse/DBZ-7108)[DBZ-7108]).
-Overall, this change is part of larger effort to remove the `replica_set` mode entirely.
-Please be sure to review your connector configurations for all MongoDB connectors when upgrading.
-
-[IMPORTANT]
-====
-This breaking change invalidates existing connector offsets and a new snapshot will be triggered by default when upgrading.
-If a snapshot is not needed or wanted, you will need to adjust your connector configuration's `snapshot.mode` accordingly.b-connection-string[connection string] to influence where to connect (https://issues.redhat.com/browse/DBZ-6521[DBZ-6521]).
-====
+* Default connection mode is changed from `replica_set` to `sharded` as a preparation step for its complete removal.
+The change will lead to invalidation of existing offsets and a silent re-execution of the initial snapshot.
+To prevent this a check was added that will fail the connector upon start if this would happen.
+The user can either set `replica_set` connection mode explicitly or can remove the existing offsets (https://issues.redhat.com/browse/DBZ-7272[DBZ-7272]).
 
 JDBC::
 
@@ -69,7 +62,6 @@ Debezium 2.5 removes the old, deprecated `ComputePartition`, and users who may s
 * The schema name prefix and letter casing for Cloud Event headers was not consistent with payload name.
 The schema name was aligned so both headers and payload share th same namespace and follow the same rules for letter casing (https://issues.redhat.com/browse/DBZ-7216[DBZ-7216]).
 
-
 == Improvements and changes
 
 In this section, we're going to take a tour of all the new features and improvements in Debezium 2.5.
@@ -523,6 +515,23 @@ Altogether, https://issues.redhat.com/issues/?jql=project%20%3D%20DBZ%20AND%20fi
 * Add tracing logs to track execution time for Debezium JDBC connector  https://issues.redhat.com/browse/DBZ-7217[DBZ-7217]
 * Validate & clarify multiple archive log destination requirements for Oracle https://issues.redhat.com/browse/DBZ-7218[DBZ-7218]
 * Upgrade logback to 1.2.13 https://issues.redhat.com/browse/DBZ-7232[DBZ-7232]
+* Add configuration option to CloudEventsConverter to customize schema type name https://issues.redhat.com/browse/DBZ-7235[DBZ-7235]
+* Support persistent history for snapshot requests for the kafka signal topic. https://issues.redhat.com/browse/DBZ-7164[DBZ-7164]
+* Change metrics endpoint of Connect REST Extensions to use the MBeanServerv directly instead of HTTP calls to the Jolokia endpoint https://issues.redhat.com/browse/DBZ-7177[DBZ-7177]
+* Metrics endpoint must handle connectors with multiple tasks (SQL Server) https://issues.redhat.com/browse/DBZ-7178[DBZ-7178]
+* DDL GRANT statement couldn't be parsed https://issues.redhat.com/browse/DBZ-7213[DBZ-7213]
+* Debezium Oracle plugin 2.5.0 Beta does not support Oracle 11g https://issues.redhat.com/browse/DBZ-7257[DBZ-7257]
+* Error during snapshot with multiple snapshot threads will not properly abort snasphostting https://issues.redhat.com/browse/DBZ-7264[DBZ-7264]
+* MySQL RDS UPDATE queries not ignored https://issues.redhat.com/browse/DBZ-7271[DBZ-7271]
+* Leaking JDBC connections https://issues.redhat.com/browse/DBZ-7275[DBZ-7275]
+* IncrementalSnapshotCaseSensitiveIT#insertDeleteWatermarkingStrategy fails https://issues.redhat.com/browse/DBZ-7276[DBZ-7276]
+* Debezium MySQL could not parse certain grant privileges. https://issues.redhat.com/browse/DBZ-7277[DBZ-7277]
+* Add PL/SQL Parser for Create Table Memoptimize https://issues.redhat.com/browse/DBZ-7279[DBZ-7279]
+* Support for Creating EDITIONABLE or NONEDITIONABLE Packages https://issues.redhat.com/browse/DBZ-7283[DBZ-7283]
+* Add PL/SQL Parser for Alter Table Memoptimize https://issues.redhat.com/browse/DBZ-7268[DBZ-7268]
+* Move metrics endpoint from UI backend to the Debezium Connect REST extension/s https://issues.redhat.com/browse/DBZ-6764[DBZ-6764]
+* website-builder image fails with newer bundler https://issues.redhat.com/browse/DBZ-7269[DBZ-7269]
+* Vitess connector build fails due to invalid GPG key https://issues.redhat.com/browse/DBZ-7280[DBZ-7280]
 
 A big thank you to all the contributors from the community who worked on Debezium 2.5:
 https://github.com/ahmedrachid[Ahmed Rachid Hazourli],
@@ -533,7 +542,6 @@ https://github.com/Naros[Chris Cranford],
 https://github.com/gunnarmorling[Gunnar Morling],
 https://github.com/harveyyue[Harvey Yue],
 https://github.com/ilyasahsan123[Ilyas Ahsan],
-https://github.com/indraraj[Indra Shukla],
 https://github.com/nicholas-fwang[Inki Hwang],
 https://github.com/jcechace[Jakub Cechacek],
 https://github.com/Jiabao-Sun[Jiabao Sun],