Release Notes for Debezium 2.7
All notable changes for Debezium releases are documented in this file. Release numbers follow Semantic Versioning.
- Release 2.7.4.Final (December 11st 2024)
- Release 2.7.3.Final (September 20th 2024)
- Release 2.7.2.Final (September 5th 2024)
- Release 2.7.1.Final (August 8th 2024)
- Release 2.7.0.Final (June 28th 2024)
- Release 2.7.0.Beta2 (June 13rd 2024)
- Release 2.7.0.Beta1 (June 6th 2024)
- Release 2.7.0.Alpha2 (May 10th 2024)
- Release 2.7.0.Alpha1 (April 25th 2024)
Release 2.7.4.Final (December 11st 2024)
See the 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 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.7.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.7.4.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.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 Quay.io.
Fixes
-
Oracle DDL parsing will fail if the DDL ends with a new line character DBZ-7040
-
Custom convert (all to strings) and SQLServer default '0' type issue DBZ-7045
-
Missing documentation for MongoDb SSL configuration DBZ-7927
-
Conditionalization implemented for single-sourcing MySQL/MariaDB content isn’t working as expected DBZ-8094
-
Error writing data to target database. (Caused by: java.lang.RuntimeException: org.postgresql.util.PSQLException: The column index is out of range: 140, number of columns: 139.) DBZ-8221
-
Debezium Server messages not being sent to Pub/Sub after restart DBZ-8236
-
JDBC Sink truncate event also add event to updateBufferByTable DBZ-8247
-
Performance Regression in Debezium Server Kafka after DBZ-7575 fix DBZ-8251
-
Error Prone library included in MySQL connector DBZ-8258
-
Debezium.text.ParsingException: DDL statement couldn’t be parsed DBZ-8259
-
DDL statement couldn’t be parsed. 'mismatched input 'NOCACHE' expecting {'AS', 'USAGE', ';'} DBZ-8262
-
journal processing loops after journal offset reset DBZ-8265
-
Embedded MySqlConnector "Unable to find minimal snapshot lock mode" since 2.5.4.Final DBZ-8271
-
Reselect Post Processor not working when pkey of type uuid etc. DBZ-8277
-
BinlogStreamingChangeEventSource totalRecordCounter is never updated DBZ-8290
-
Race condition in stop-snapshot signal DBZ-8303
-
ReselectPostProcessor fails when reselecting columns from Oracle DBZ-8304
-
Debezium MySQL DDL parser: SECONDARY_ENGINE=RAPID does not support DBZ-8305
-
Oracle DDL failure - subpartition list clause does not support in-memory clause DBZ-8315
-
DDL statement couldn’t be parsed DBZ-8316
-
Oracle connector: archive.log.only.mode stop working after reach SYSDATE SCN DBZ-8345
-
Object name is not in the list of S3 schema history fields DBZ-8366
-
Upgrade protobuf dependencies to avoid potential vulnerability DBZ-8371
-
ExtractNewRecordState transform: NPE when processing non-envelope records DBZ-8393
-
Oracle LogMiner metric OldestScnAgeInMilliseconds can be negative DBZ-8395
-
ExtractNewDocumentStateTestIT fails randomly DBZ-8397
-
Oracle OBJECT_ID lookup and cause high CPU and latency in Hybrid mining mode DBZ-8399
-
Engine shutdown may get stuck when error is thrown during connector stop DBZ-8414
-
JdbcOffsetBackingStore does not release lock of debezium_offset_storage gracefully DBZ-8423
-
Installation documentation typo on download link DBZ-8429
-
Asycn engine fails with NPE when transformation returns null DBZ-8434
-
Formatting characters render in descriptions of Oracle
log.mining
properties DBZ-8450
Other changes
-
Fix conditionalization in shared MariaDB/MySQL file DBZ-8254
-
Add Oracle FUTC license DBZ-8260
-
Remove Oracle libs from product assembly package DBZ-8261
-
debezium-connector-binlog does not need MariaDB dependency DBZ-8263
-
Provide subset package for Debezium Server DBZ-8264
-
BlockingSnapshotIT streamingMetricsResumeAfterBlockingSnapshot fails after backport DBZ-8267
-
Correct description of the
all_tables
option for the PGpublication.autocreate.mode
property DBZ-8268 -
Test docs for productization and fix broken links and rendering errors DBZ-8284
-
Formatting characters render literally in docs DBZ-8293
-
Backport two fixes to binlog client version 0.31.x DBZ-8387
-
Log SCN existence check may throw ORA-01291 if a recent checkpoint occurred DBZ-8389
Release 2.7.3.Final (September 20th 2024)
See the 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 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.7.3.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.7.3.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.3.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 Quay.io.
Fixes
-
Make ORA-00600 - krvrdccs10 automatically retriable DBZ-5009
-
DDL statement couldn’t be parsed: REVOKE IF EXISTS DBZ-8209
-
Oracle TableSchemaBuilder provides wrong column name in error message DBZ-8217
-
Debezium does not restart automatically after throwing an ORA-00600 krvrdccs30 error DBZ-8223
-
JDBC sink doesn’t include fields as per documentation DBZ-8224
-
Unbounded number of processing threads in async engine DBZ-8237
-
Streaming metrics are stuck after an ad-hoc blocking snapshot DBZ-8238
-
DDL statement couldn’t be parsed with IF EXISTS DBZ-8240
-
Random engine factory used by default DBZ-8241
Other changes
-
Implement separate source and sink connector sections in documentation navigation DBZ-8220
-
Broken link to Streams doc about configuring logging DBZ-8231
-
Document passthrough hibernate.* properties for the JDBC connector DBZ-8232
-
AbstractConnectorTest consumeRecordsUntil may prematurely exit loop DBZ-8250
Release 2.7.2.Final (September 5th 2024)
See the 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 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.7.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.7.2.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.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 Quay.io.
Breaking changes
When using Kafka sink it was possible that Debezium Server was blocked indefinitely in case of broken connection to Kafka broker. This is no longer the case as a delivery timeout with default value was introduced (DBZ-7575).
When SQL Server connector was configured to run in mutliple tasks the JMX signalling an notification was not working for all of them. This is fixed but the JMX naming was updated to reflect the task id (DBZ-8137).
Fixes
-
Incremental snapshots don’t work with CloudEvent converter DBZ-7601
-
Incremental snapshot fails with NPE if surrogate key doesn’t exist DBZ-7797
-
Postgres connector - null value processing for "money" type column. DBZ-8027
-
Using snapshot.include.collection.list with Oracle raises NullPointerException DBZ-8032
-
Performance degradation when reconstructing (log.mining.stragtegy hybrid mode) DBZ-8071
-
ORA-00600: internal error code, arguments: [krvrdGetUID:2], [18446744073709551614], [], [], [], [], [], [], [], [], [], [] DBZ-8125
-
ConvertingFailureIT#shouldFailConversionTimeTypeWithConnectModeWhenFailMode fails randomly DBZ-8128
-
Unpredicatable ordering of table rows during insertion causing foreign key error DBZ-8130
-
schema_only crashes ibmi Connector DBZ-8131
-
Support larger database.server.id values DBZ-8134
-
Open redo thread consistency check can lead to ORA-01291 - missing logfile DBZ-8144
-
SchemaOnlyRecoverySnapshotter not registered as an SPI service implementation DBZ-8147
-
When stopping the Oracle rac node the Debezium server throws an expections - ORA-12514: Cannot connect to database and retries DBZ-8149
-
Issue with Debezium Snapshot: DateTimeParseException with plugin pgoutput DBZ-8150
-
JDBC connector validation fails when using record_value with no primary.key.fields DBZ-8151
-
Taking RAC node offline and back online can lead to thread inconsistency DBZ-8162
-
Postgres JSONB Fields are not supported with Reselect Post Processor DBZ-8168
-
NullPointerException (schemaUpdateCache is null) when restarting Oracle engine DBZ-8187
-
XStream may fail to attach on retry if previous attempt failed DBZ-8188
-
Exclude Oracle 23 VECSYS tablespace from capture DBZ-8198
-
AbstractProcessorTest uses an incorrect database name when run against Oracle 23 Free edition DBZ-8199
Other changes
-
Documentation for signals provides incorrect data-collection format for some connectors DBZ-8090
-
Add LogMiner start mining session retry attempt counter to logs DBZ-8143
-
Reduce logging verbosity of XStream DML event data DBZ-8148
-
Add MariaDB connector server distribution DBZ-8186
-
Reduce log verbosity of OpenLogReplicator SCN confirmation DBZ-8201
Release 2.7.1.Final (August 8th 2024)
See the 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 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.7.1.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.7.1.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.1.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 Quay.io.
New features
-
Update third-party LICENSE with LGPL forMariaDB Connector/J DBZ-8099
Fixes
-
Clarify that Oracle connector does not read from physical standby DBZ-7895
-
JdbcSinkTask doesn’t clear offsets on stop DBZ-7946
-
Issue with Hybrid mode and DDL change DBZ-7991
-
Incorrect offset/history property mapping generatated DBZ-8007
-
StackOverflow exception on incremental snapshot DBZ-8011
-
JDBC primary.key.fields cannot be empty when i set insert.mode to upsert and primary.key.mode record_value DBZ-8018
-
Unable to acquire buffer lock, buffer queue is likely full DBZ-8022
-
ORA-65090: operation only allowed in a container database when connecting to a non-CDB database DBZ-8023
-
Added type to Prometheus JMX exporter DBZ-8036
-
Add
kafka.producer
metrics to debezium-server jmx exporter config DBZ-8037 -
"Unexpected input: ." when snapshot incremental empty Database DBZ-8050
-
Oracle connector inconsistency in redo log switches DBZ-8055
-
Blocking snapshot can fail due to CommunicationsException DBZ-8058
-
ParsingException (MySQL/MariaDB): rename table syntax DBZ-8066
-
Oracle histogram metrics are no longer printed in logs correctly DBZ-8068
-
In hybrid log.mining.strategy reconstruction logs should be set to DEBUG DBZ-8070
-
Support capturing BLOB column types during snapshot for MySQL/MariaDB DBZ-8076
-
Vitess transaction Epoch should not reset to zero when tx ID is missing DBZ-8087
-
After changing the column datatype from int to float the Debezium fails to round it and i get a null value for this field in the stream DBZ-8089
-
MySQL and MariaDB keyword YES cannot be parsed as a column name DBZ-8092
-
NotificationIT tests seemingly seem to fail due to stepping on one another DBZ-8100
-
ORA-26928 - Unable to communicate with XStream apply coordinator process should be retriable DBZ-8102
-
Transformations are not closed in emebdded engine DBZ-8106
-
Don’t close connection after loading timescale metadata in TimescaleDb SMT DBZ-8109
-
Primary Key Update/ Snapshot Race Condition DBZ-8113
-
Docs: connect-log4j.properties instead log4j.properties DBZ-8117
-
Recalculating mining range upper bounds causes getScnFromTimestamp to fail DBZ-8119
Other changes
-
Document new MariaDB connector DBZ-7786
-
Bump Infinispan to 14.0.29.Final DBZ-8010
-
Add disclaimer that PostProcessors and CustomConverters are Debezium source connectors only DBZ-8031
-
Conditionalize reference to the MySQL default value in description of
schema.history.internal.store.only.captured.databases.ddl
DBZ-8081 -
Add MariaDB to debezium/connect image DBZ-8088
-
Converters documentation uses incorrect examples DBZ-8104
-
Remove reference to`additional condition` signal parameter from ad hoc snapshots doc DBZ-8107
-
TimescaleDbDatabaseTest.shouldTransformCompressedChunks is failing DBZ-8123
-
Update Oracle connector doc to describe options for restricting access permissions for the Debezium LogMiner user DBZ-8124
Release 2.7.0.Final (June 28th 2024)
See the 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 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.7.0.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.7.0.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.0.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 Quay.io.
Fixes
-
Unable to use resume token of some documents with composite IDs DBZ-6522
-
Quarkus generates VSC kubernetes annotations pointing to a fork DBZ-7415
-
MongoDB documentation still mentions replica_set connection mode DBZ-7862
-
Clarify documentation for log.mining.archive.destination.name Oracle configuration property DBZ-7939
-
Ad-hoc snapshot raises ORA-00911 when table name uses non-standard characters requiring quotations DBZ-7942
-
Exclude signaling data collection from the snapshot process DBZ-7944
-
JDBC sink time tests fail due to increased precision with SQL Server DBZ-7949
-
Commit is not called after DDLs in JDBC stores DBZ-7951
-
Database case sensitivity can lead to NullPointerException on column lookups DBZ-7956
-
Debezium ibmi connector drops journal entries DBZ-7957
-
Error counter reset in poll() can cause infinite retries DBZ-7964
-
Oracle DDL parser fails using NOMONITORING clause DBZ-7967
-
Invalid default DSimage used for nighly/snapshot operator version DBZ-7970
-
Mongo Oversized Document FAQ documentation issue DBZ-7987
-
Cassandra connector does not work with 2.6.1 Server DBZ-7988
-
Testcontainers tests fails on newer versions of Docker DBZ-7986
Other changes
-
Document the use of the "source" prefix usage for table name formats DBZ-6618
-
Remove dependency on MySQL driver, add custom CharacterSet Mapper DBZ-7783
-
Rebase website-builder image on Ruby 3.2 DBZ-7916
-
Warn about incompatible usage of read.only property for PostgreSQL DBZ-7947
-
Run JDBC sink tests for any relational connector pull requests DBZ-7948
-
Bump Quarkus to 3.12.0 for Quarkus Outbox Extension DBZ-7961
-
Bump Hibernate dependency to 6.4.8.Final DBZ-7969
-
Deprecated EmbeddedEngine DBZ-7976
Release 2.7.0.Beta2 (June 13rd 2024)
See the 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 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.7.0.Beta2 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.7.0.Beta2 plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.0.Beta2 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 Quay.io.
Breaking changes
PostgreSQL 10 and 11 are end of life for one or more years. Debezium now supports both versions as best effort only. No testing is done and no issues specific to these two versions will be proactively fixed by the core team. The community contributions will be accepted (DBZ-7128).
Fixes
-
Oracle property column.truncate.to.length.chars does not support length zero DBZ-7079
-
Debezium Server cannot pass empty string to Kafka config DBZ-7767
-
Unable To Exclude Column Using Configuration DBZ-7813
-
Oracle connector failed to work when the table name contains single quote DBZ-7831
-
Incorrect documentation for CE type DBZ-7926
-
DDL statement couldn’t be parsed DBZ-7931
-
SQL Server default value resolution for TIME data types causes precision loss DBZ-7933
-
Incorrect name of JMX Exporter k8s service DBZ-7934
-
OlrNetworkClient does not disconnect when error occurs DBZ-7935
-
Multiple ARRAY types in single table causing error DBZ-7938
Release 2.7.0.Beta1 (June 6th 2024)
See the 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 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.7.0.Beta1 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.7.0.Beta1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.0.Beta1 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 Quay.io.
Breaking changes
Debezium snapshots were orginally being deployed to the legacy oss.sonatype.org
Sonatype infrastucture. This has changed and they are now deployed to the new s01.oss.sonatype.org
infrastructure (DBZ-7641).
Oracle NUMERIC
type with zero scale ignored decimal.handling.mode
setting. With this version the type is properly propagated as configured type. This can cause an issue with upgrade for deployments with strict schema registry compatibility rules (DBZ-7882).
New features
-
debezium-connector-db2: z/OS integration DBZ-4812
-
Ensure vgtid remains local to shards streamed by task DBZ-6721
-
Decompose provide.transaction.metadata into components DBZ-6722
-
Handle Enum as String or Int DBZ-7792
-
MariaDB target should support 'upsert' for insert.mode DBZ-7874
-
Add support for user/password authentication in Nats Jetstream sink adapter DBZ-7876
-
Allow customizing ObjectMapper in JsonSerde DBZ-7887
-
Add configurable delay after successful snapshot before starting streaming DBZ-7902
-
Enhancing the threads utility class for broader use DBZ-7906
-
Include Prometheus JMX exporter in Debezium Server distribution DBZ-7913
-
Add support for TLS auth for NATS JetStream sink DBZ-7922
Fixes
-
Debezium 1.9.2 cannot capture field that is date type of postgres DBZ-5182
-
Rewrite batch statement not supported for jdbc debezium sink DBZ-7845
-
Debezium MySQL Snapshot Connector Fails DBZ-7858
-
Reduce enum array allocation DBZ-7859
-
Snapshot retrying logic falls into infinite retry loop DBZ-7860
-
Bump Java in Debezium Server images DBZ-7861
-
Default value of error retries not interpreted correctly DBZ-7870
-
Avro schema compatibility issues when upgrading from Oracle Debezium 2.5.3.Final to 2.6.1.Final DBZ-7880
-
Improve offset and history storage configuration DBZ-7884
-
Oracle Debezium Connector cannot startup due to failing incremental snapshot DBZ-7886
-
Multiple completed reading from a capture instance notifications DBZ-7889
-
Debezium can’t handle columns with # in its name DBZ-7893
-
Oracle interval default values are not properly parsed DBZ-7898
-
Debezium server unable to shutdown on pubsub error DBZ-7904
-
Handle gtid without range only single position DBZ-7905
-
Oracle connector cannot parse SUBPARTITION when altering table DBZ-7908
-
Make column exclude use keyspace not shard DBZ-7910
-
The explanation in the documentation is insufficient - metric DBZ-7912
Release 2.7.0.Alpha2 (May 10th 2024)
See the 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 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.7.0.Alpha2 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.7.0.Alpha2 plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.0.Alpha2 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 Quay.io.
New features
-
Add ROW_ID as part of source information block for LogMiner sources DBZ-4332
-
Support for ARRAY data types for postgres DBZ-7752
-
Enhance documentation about using tags to customize connector snapshot/streaming MBean names DBZ-7800
-
Allow specifying the log mining flush table with an optional schema DBZ-7819
-
Added nats JWT/seed authentication config options DBZ-7829
-
Update Debezium container images to use Fedora 38 DBZ-7832
-
Debezium oracle connectors needs to support IN clause for log miner query for more than 1000 tables as it creates performance issue DBZ-7847
Fixes
-
Debezium User Guide 2.5.4: Grammatical error DBZ-7803
-
> io.debezium.text.ParsingException : SQL Contains Partition DBZ-7805
-
Ad-hoc blocking snapshot not working through file channeling without inserting a row in the database. DBZ-7806
-
Postgres: Potential data loss on connector restart DBZ-7816
-
Abnormal Behavior in Debezium Monitoring Example - mysql connector DBZ-7826
-
DEBEZIUM_VERSION is wrongly set to 2.6.0.Alpha1 DBZ-7827
-
Sql Server incorrectly applying quoted snapshot statement overrides DBZ-7828
-
Debezium JDBC Sink not handle order correctly DBZ-7830
-
Fix typo in documentation/modules doc DBZ-7844
-
Support Oracle DDL Alter Audit Policy DBZ-7864
-
Support Oracle DDL Create Audit Policy DBZ-7865
Other changes
-
Log exception details early in case MySQL keep-alive causes deadlock on shutdown DBZ-7570
-
Extend mongodb system tests with ssl option DBZ-7605
-
Refactor oracle connector test job DBZ-7807
-
Fix anchor ID collisions that prevent downstream documentation from building DBZ-7815
-
Add c3p0 timeout configuration example to JDBC sink DBZ-7822
-
Move undocumented option to internal DBZ-7833
-
Increase wait for shouldGracefullySkipObjectBasedTables on XStream DBZ-7839
-
Bump Debezium Server to Quarkus 3.8.3 DBZ-7841
-
Bump Outbox Extension to Quarkus 3.10.0 DBZ-7842
-
in the Cassandra documentation, there is a typo which should have been disable not Dusable. DBZ-7851
Release 2.7.0.Alpha1 (April 25th 2024)
See the 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 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.7.0.Alpha1 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.7.0.Alpha1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.7.0.Alpha1 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 Quay.io.
Breaking changes
JDBC queries could hang indefinitely in case of database error communication. A configurable timeout was introduced to prevent the issue (DBZ-7616).
SQL Server connector by default processed all transactions available during each data poll. This could lead to out of memeory errors for databases with a large traffic. The default value was changed to limit the number of transactions to 500
(DBZ-7750).
New features
-
Support helm chart installation of debezium-operator DBZ-7116
-
Adding additional-conditions into Incremental Snapshot to MongoDB DBZ-7138
-
Document MongoDB connector inactivity pause and it’s performance implications DBZ-7147
-
Move MariaDB connector from MySQL to its own separate connector DBZ-7693
-
Mongodb Delete events should have
_id
in the payload DBZ-7695 -
Provide option to encode ordering metadata in each record DBZ-7698
-
Manage escaping when captured table are determined for snapshot DBZ-7718
-
Performance improve in KafkaRecordEmitter class DBZ-7722
-
Introduce
RawToString
transform for converting GUIDs stored in OracleRAW(16)
columns to Guid string DBZ-7753 -
Improve NLS character set support by including orai18n dependency DBZ-7761
-
Vitess Connector should have parity with MySQL’s time.precision.mode DBZ-7773
-
Document potential null values in the after field for lookup full update type DBZ-7789
-
Fix invalid date/timestamp check & logging level DBZ-7811
Fixes
-
Builtin database name filter is incorrectly applied only to collections instead of databases in snapshot DBZ-7485
-
After the initial deployment of Debezium, if a new table is added to MSSQL, its schema is was captured DBZ-7697
-
The test is failing because wrong topics are used DBZ-7715
-
Incremental Snapshot: read duplicate data when database has 1000 tables DBZ-7716
-
Handle instability in JDBC connector system tests DBZ-7726
-
SQLServerConnectorIT.shouldNotStreamWhenUsingSnapshotModeInitialOnly check an old log message DBZ-7729
-
Fix MongoDB unwrap SMT test DBZ-7731
-
Snapshot fails with an error of invalid lock DBZ-7732
-
Column CON_ID queried on V$THREAD is not available in Oracle 11 DBZ-7737
-
Redis NOAUTH Authentication Error when DB index is specified DBZ-7740
-
Getting oldest transaction in Oracle buffer can cause NoSuchElementException with Infinispan DBZ-7741
-
The MySQL Debezium connector is not doing the snapshot after the reset. DBZ-7743
-
MongoDb connector doesn’t work with Load Balanced cluster DBZ-7744
-
Align unwrap tests to respect AT LEAST ONCE delivery DBZ-7746
-
Exclude reload4j from Kafka connect dependencies in system testsuite DBZ-7748
-
Pod Security Context not set from template DBZ-7749
-
Apply MySQL binlog client version 0.29.1 - bugfix: read long value when deserializing gtid transaction’s length DBZ-7757
-
Change streaming exceptions are swallowed by BufferedChangeStreamCursor DBZ-7759
-
Sql-Server connector fails after initial start / processed record on subsequent starts DBZ-7765
-
Valid resume token is considered invalid which leads to new snapshot with some snapshot modes DBZ-7770
-
NO_DATA snapshot mode validation throw DebeziumException on restarts if snapshot is not completed DBZ-7780
-
DDL statement couldn’t be parsed DBZ-7788
-
old class reference in ibmi-connector services DBZ-7795
-
Documentation for Debezium Scripting mentions wrong property DBZ-7798
Other changes
-
Update documenation for embedded engine DBZ-7632
-
Implement basic JHM perf. tests for async engine DBZ-7633
-
Upgrade Debezium Quarkus Outbox to Quarkus 3.9.2 DBZ-7663
-
Move LogPositionValidator outside the JdbcConnection DBZ-7717
-
Fix mongodb image in system tests DBZ-7739
-
Refactor exporting to CloudEvents DBZ-7755
-
Use thread cap only for deault value DBZ-7763
-
Evaluate cached thread pool as the default option for async embedded engine DBZ-7764
-
Create JMH benchmark for engine record processing DBZ-7776
-
Improve processing speed of async engine processors which use List#get() DBZ-7777
-
Disable renovate in debezium-ui DBZ-7814