Release Notes for Debezium 2.4

All notable changes for Debezium releases are documented in this file. Release numbers follow Semantic Versioning.

Release 2.4.2.Final (December 13rd 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.2.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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

There are no breaking changes in this release.

New features

There are no new features in this release.

Fixes

  • Debezium-ddl-parser crashes on parsing MySQL DDL statement (specific UPDATE) DBZ-7152

  • Log sequence check should treat each redo thread independently DBZ-7158

  • Parsing MySQL indexes for JSON field fails, when casting is used with types double and float DBZ-7189

  • Unchanged toasted array columns are substituted with unavailable.value.placeholder, even when REPLICA IDENTITY FULL is configured. DBZ-7193

  • Broken support for multi-namespace watching DBZ-7254

Other changes

There are no other changes in this release.

Release 2.4.1.Final (November 16th 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.1.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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.

Breaking changes

There are no breaking changes in this release.

New features

  • Provide capability to set image pull secrets in DS k8s CRD DBZ-6962

  • Add displayName and description metadata to DebeziumServer CRD in OLM Bundle DBZ-7011

  • Provide resources to set pod requests and limits in DS k8s CRD DBZ-7052

  • Provide svc to better collects dbz-server metrics in DS k8s DBZ-7053

Fixes

  • Oracle RAC throws ORA-00310: archive log sequence required DBZ-5350

  • oracle missing CDC data DBZ-5656

  • Missing oracle cdc records DBZ-5750

  • Multiple debezium:offsets Redis clients DBZ-6952

  • Wrong case-behavior for non-avro column name in sink connector DBZ-6958

  • Missing events from Oracle 19c DBZ-6963

  • Handle properly bytea field for jdbc sink to postgresql DBZ-6967

  • Debezium jdbc sink process truncate event failure DBZ-6970

  • Debezium jdbc sink should throw not supporting schema change topic exception DBZ-6990

  • OLM bundle version for GA releases is invalid DBZ-6994

  • ALTER TABLE fails when adding multiple columns to JDBC sink target DBZ-6999

  • Invalid Link to zulip chat in CSV metadata DBZ-7000

  • Make sure to terminate the task once connectivity is lost to either the rebalance or sync topic DBZ-7001

  • Missing .metadata.annotations.repository field in CSV metadata DBZ-7003

  • Single quote replication and loss of data DBZ-7006

  • Oracle connector: Payload size over 76020 bytes are getting truncated DBZ-7018

  • DDL statement couldn’t be parsed DBZ-7030

  • Debezium Embedded Infinispan Performs Slowly DBZ-7047

  • Field exclusion does not work with events of removed fields DBZ-7058

  • Debezium crashes on parsing MySQL DDL statement (specific INSERT) DBZ-7119

  • Debezium-ddl-parser crashes on parsing MySQL DDL statement (specific UNION) DBZ-7140

Other changes

  • Further refactoring to correct downstream rendering of incremental snapshots topics DBZ-6997

  • Use optional schema for Timezone Converter tests DBZ-7020

  • Update operator dependencies and add qosdk platform bom DBZ-7048

  • Consolidate resource labels and annotations DBZ-7064

  • Allow DS JMX to use username-password authentication on k8 DBZ-7087

Release 2.4.0.Final (October 3rd 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.0.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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.

Breaking changes

There are no breaking changes in this release.

New features

  • Add timestamp to Notification DBZ-6793

  • Documentation for cursor.oversize.skip.threshold is missing units DBZ-6968

  • Add MongoDB Connector support for filtering.match.mode=regex|literal property DBZ-6973

Fixes

  • Debezium Outbox not working with CloudEventsConverter DBZ-3642

  • Incremental snapshot data-collections are not deduplicated DBZ-6787

  • MongoDB connector no longer requires cluster-wide privileges DBZ-6888

  • Timezone Transformation can’t work DBZ-6940

  • MySQL Kafka Signalling documentation is incorrect DBZ-6941

  • Infinite loop when using OR condition in additional-condition DBZ-6956

  • Filter out specified DDL events logic is reverted DBZ-6966

  • DDL parser does not support NOCOPY keyword DBZ-6971

  • Decrease time spent in handling rebalance events DBZ-6974

  • ParsingException (MySQL/MariaDB): User specification with whitespace DBZ-6978

  • RecordsStreamProducerIT#shouldReceiveChangesForInfinityNumericWithInfinity fails on Postgres < 14 DBZ-6986

  • PostgresConnectorIT#shouldAddNewFieldToSourceInfo may fail as the schema may not exists DBZ-6987

Other changes

  • Add option to use apicurio with TLS to system level testsuite DBZ-6954

Release 2.4.0.CR1 (September 22nd 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.0.CR1 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.4.0.CR1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.0.CR1 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

Vitess connector was retrying only a subset of errors by default. This behaviour is changed and only explicitly defined errors are not retried (DBZ-6944).

New features

  • Update mongodb incremental snapshot to allow multiple threads reading chunks DBZ-6518

  • Support for GKE workload identities DBZ-6885

  • Support for PostgreSQL 16 DBZ-6911

  • Vitess connector should retry on not found errors DBZ-6939

Fixes

  • Ad-hoc blocking snaps trigger emits schema changes of all tables DBZ-6828

  • When the start_scn corresponding to the existence of a transaction in V$TRANSACTION is 0, log mining starts from the oldest scn when the oracle connector is started for the first time DBZ-6869

  • Ensure that the connector can handle rebalance events robustly DBZ-6870

  • OpenLogReplicator confirmation can resend or omit events on restarts DBZ-6895

  • ExtractNewRecordState’s schema cache is not updated with arrival of the ddl change event DBZ-6901

  • Misleading Debezium error message when RDI port is not specified in application.properties DBZ-6902

  • Generting protobuf files to target/generated-sources breaks build DBZ-6903

  • Clean log printout in Redis Debezium Sink DBZ-6908

  • Values being omitted from list of JSON object DBZ-6910

  • fix logger named DBZ-6935

  • MySql connector get NPE when snapshot.mode is set to never and signal data collection configured DBZ-6937

  • Sanity check / retry for redo logs does not work per Oracle RAC thread DBZ-6938

  • Drop events has wrong table changes information DBZ-6945

  • Remove spaces from Signal and Notification MBean’s ObjectName DBZ-6957

Other changes

  • Migrate all examples from mongodb.hosts to mongodb.connection.string DBZ-6893

Release 2.4.0.Beta2 (September 13rd 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.0.Beta2 plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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

Deprecated MongoDB connection connfiguration via mongodb.hosts and mongodb.members.autodiscover options was removed. Only configuration via connection string is now supported (DBZ-6892).

New features

  • Ingest changes via OpenLogReplicator DBZ-2543

  • Only publish deltas instead of full snapshots to reduce size of sync event messages DBZ-6458

  • SMT for handling timezone conversions DBZ-6567

  • Support custom authentication on MongoDB connector DBZ-6741

  • Document mongodb.authentication.class DBZ-6788

  • Support truncating large columns DBZ-6844

  • Always reset VStream grpc channel when max size is exceeded DBZ-6852

  • Add an overview page for Connector detail DBZ-6856

  • Avoid getting NPE when executing the arrived method in ExecuteSnapshot DBZ-6865

  • Configurable order of user defined and internal aggregation pipeline DBZ-6872

  • Add support for MongoDB 7 DBZ-6882

Fixes

  • Documentation content section in the debezium.io scroll over to the top header. DBZ-5942

  • Postgres - Incremental snapshot fails on tables with an enum type in the primary key DBZ-6481

  • schema.history.internal.store.only.captured.databases.ddl flag not considered while snapshot schema to history topic DBZ-6712

  • ExtractNewDocumentState for MongoDB ignore previous document state when handling delete event’s with REWRITE DBZ-6725

  • MongoDB New Document State Extraction: original name overriding does not work DBZ-6773

  • Error with propagation source column name DBZ-6831

  • Kafka offset store fails with NPE DBZ-6853

  • JDBC Offset storage - configuration of table name does not work DBZ-6855

  • JDBC sink insert fails with Oracle target database due to semicolon DBZ-6857

  • Oracle test shouldContinueToUpdateOffsetsEvenWhenTableIsNotChanged fails with NPE DBZ-6860

  • Tombstone events causes NPE on JDBC connector DBZ-6862

  • Debezium-MySQL not filtering AWS RDS internal events DBZ-6864

  • errors.max.retries = 0 Causes retrievable error to be ignored DBZ-6866

  • Streaming aggregation pipeline broken for combination of database filter and signal collection DBZ-6867

  • ChangeStream aggregation pipeline fails on large documents which should be excluded DBZ-6871

  • Oracle alter table drop constraint fails when cascading index DBZ-6876

Other changes

  • Docs for Timezone SMT DBZ-6835

  • Write a blog post for custom properties step in DBZ UI DBZ-6838

  • Improve website/documentation artifact links DBZ-6850

  • Add possibility to add on-demand adjusted testing farm execution DBZ-6854

  • Oracle connector test suite logging no longer works DBZ-6859

  • Increase Oracle log level to DEBUG for several key important log messages DBZ-6880

  • Document cursor pipeline ordering and oversize document handling mode DBZ-6883

Release 2.4.0.Beta1 (August 29th 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.0.Beta1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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

Oracle SCN metrics were exposed as strings. This could prevent ceratin tools like JMX exporter from scraping them. Debezium currently exposes them as numerc BigInteger (DBZ-6798).

New features

  • Provide by DDL type schema event filtering DBZ-6240

  • Add support for TimescaleDB DBZ-6482

  • Max transaction duration for Oracle connector DBZ-6615

  • Debezium 2.3.0.Final Missing Kafka Channel Documentation DBZ-6688

  • Make the Kafka channel consumer group ID configurable for the PostgreSQL connector DBZ-6689

  • Use JSON format for JMX Notification userData DBZ-6742

  • Use custom RowDeserializers in case of binlog compression DBZ-6786

  • Create a shardless topic naming strategy for vitess connector DBZ-6800

  • JDBC sink does not support SQL Server identity inserts DBZ-6801

  • Allow the embedded infinispan global configuration to be configurable DBZ-6808

  • SqlServer connector send heartbeats when there is no change in the DB DBZ-6811

  • Make finished partition deletion delay configurable. DBZ-6814

  • Add vcs.xml for idea DBZ-6825

  • Make partial and multi-response transactions debug level logs DBZ-6830

Fixes

  • Debezium heartbeat.action.query does not start before writing to WAL. DBZ-6635

  • Schema name changed with Custom topic naming strategy DBZ-6641

  • Wrong behavior of quote.identifiers in JdbcSinkConnector DBZ-6682

  • Toasted UUID array is not properly processed DBZ-6720

  • Debezium crashes on parsing MySQL DDL statement (specific JOIN) DBZ-6724

  • When using pgoutput in postgres connector, (+/-)Infinity is not supported in decimal values DBZ-6758

  • Outbox transformation can cause connector to crash DBZ-6760

  • MongoDB New Document State Extraction: nonexistent field for add.headers DBZ-6774

  • Mongodb connector tests are massively failing when executed on 7.0-rc version DBZ-6779

  • Dbz crashes on parsing MySQL DDL statement (SELECT 1.;) DBZ-6780

  • Mysql connector tests are failing when executed without any profile DBZ-6791

  • Dbz crashed on parsing MySQL DDL statement (SELECT 1 + @sum:=1 AS ss;) DBZ-6794

  • MySQL DDL parser - REPEAT function not accepted DBZ-6803

  • Fix bug with getsnapshottingtask DBZ-6820

  • Dbz crashes on DDL statement (non Latin chars in variables) DBZ-6821

  • Not trim the default value for the BIGINT and SMALLINT types when parsing MySQL DDL DBZ-6824

  • PostgresConnectorIT#shouldAddNewFieldToSourceInfo fails randomly DBZ-6839

  • Wrong filtered comments DBZ-6840

  • Intermittend test failure: BaseSourceTaskTest.verifyTaskRestartsSuccessfully DBZ-6841

Other changes

  • Upstream documentation connector config is not unified DBZ-6704

  • Blocking snapshot must take snapshot configurations from signal DBZ-6731

  • Documentation Request - Property File Configuration - Off-Heap Event Buffering with Embedded Infinispan DBZ-6813

  • Onboard testing farm DBZ-6827

  • When using skip.messages.without.change=true a WARN log message is reported for each record DBZ-6843

Release 2.4.0.Alpha2 (August 9th 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 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.4.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.4.0.Alpha2 plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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.

Breaking changes

Debezium Server package provided only Cassandra 4 connector. All connectors are now provided but an environment variable must be configured to select the one to use (DBZ-6638).

MySQL did not set precision for BIGINT in precise mode. The precision is now set which can lead to a schema incompatibility (DBZ-6714).

Default value for default Oracle LogMiner query fetch size was increase to 10000 (DBZ-6729).

Vitess connector mapped _bin collated string columns to binary data. The columns are now correctly mapped to strings (DBZ-6748).

Vitess connector previously applied schema changes across all shards. The schema changes are now correctly applied for each shard individually (DBZ-6775). If you are using a io.debezium.schema.DefaultTopicNamingStrategy (or a derivative) then you should switch to io.debezium.connector.vitess.TableTopicNamingStrategy to preserve the same topics. Now the DefaultTopicNamingStrategy will route messages to topics based on which shard the change occurred in.

New features

  • Switch tracing to OpenTelemetry DBZ-2862

  • Update the Edit connector UI to incorporate the feedback received from team in demo DBZ-6514

  • Support blocking ad-hoc snapshots DBZ-6566

  • Add new parameters to RabbitMQ consumer DBZ-6581

  • Document read preference changes in 2.4 DBZ-6591

  • Log appropriate error when JDBC connector receive SchemaChange record DBZ-6655

  • Send tombstone events when partition queries are finished DBZ-6658

  • Propagate source column name and allow sink to use it DBZ-6684

  • Disable jdk-outreach-workflow.yml in forked personal repo DBZ-6702

  • Support alternative JDBC drivers in MySQL connector DBZ-6727

  • Add STOPPED and RESTARTING connector states to testing library DBZ-6734

  • Add a new parameter for selecting the db index when using Redis Storage DBZ-6759

  • Table schemas should be updated for each shard individually DBZ-6775

Fixes

  • Connector drop down causes a scroll bar DBZ-5421

  • Provide outline for drawer component showing connector details DBZ-5831

  • Modify scroll for the running connector component DBZ-5832

  • Connector restart regression DBZ-6213

  • Document Optimal MongoDB Oplog Config for Resiliency DBZ-6455

  • JDBC Schema History: When the table name is passed as dbName.tableName, the connector does not start DBZ-6484

  • Oracle DDL parser does not properly detect end of statement when comments obfuscate the semicolon DBZ-6599

  • Received an unexpected message type that does not have an 'after' Debezium block DBZ-6637

  • When Debezium Mongodb connector encounter authentication or under privilege errors, the connection between debezium and mongodb keeps going up. DBZ-6643

  • Snapshot will not capture data when signal.data.collection is present without table.include.list DBZ-6669

  • Retriable operations are retried infinitely since error handlers are not reused DBZ-6670

  • Oracle DDL parser does not support column visibility on ALTER TABLE DBZ-6677

  • Partition duplication after rebalances with single leader task DBZ-6685

  • JDBC Sink Connector Fails on Loading Flat Data Containing Struct Type Fields from Kafka DBZ-6686

  • SQLSyntaxErrorException using Debezium JDBC Sink connector DBZ-6687

  • Should use topic.prefix rather than connector.server.name in MBean namings DBZ-6690

  • CDC - Debezium x RabbitMQ - Debezium Server crashes when an UPDATE/DELETE on source database (PostgreSQL) DBZ-6691

  • Missing operationTime field on ping command when executed against Atlas DBZ-6700

  • MongoDB SRV protocol not working in Debezium Server DBZ-6701

  • Custom properties step not working correctly in validation of the properties added by user DBZ-6711

  • Add tzdata-java to UI installation Dockerfile DBZ-6713

  • Refactor EmbeddedEngine::run method DBZ-6715

  • Oracle fails to process a DROP USER DBZ-6716

  • Oracle LogMiner mining distance calculation should be skipped when upper bounds is not within distance DBZ-6733

  • MariaDB: Unparseable DDL statement (ALTER TABLE IF EXISTS) DBZ-6736

  • MySQL dialect does not properly recognize non-default value longblob types due to typo DBZ-6753

  • Postgres tests for toasted byte array and toasted date array fail with decoderbufs plugin DBZ-6767

  • Notifications and signals leaks between MBean instances when using JMX channels DBZ-6777

  • Oracle XML column types are not properly resolved when adding XMLTYPE column during streaming DBZ-6782

Other changes

  • Highlight information about how to configure the schema history topic to store data only for intended tables DBZ-6219

  • Blogpost about custom signalling/notification channels DBZ-6478

  • NotificationIT with Oracle xstream fails randomly DBZ-6672

  • Flaky Oracle test: shouldCaptureChangesForTransactionsAcrossSnapshotBoundaryWithoutReemittingDDLChanges DBZ-6673

  • Update documentation on XML and RAW data types DBZ-6676

  • Use descriptive text instead of ‘-1’ in ‘Time since last event’ for no event case DBZ-6681

  • MongoDB upstream documentation duplication DBZ-6705

  • Upstream documentation missing types for configurations DBZ-6707

  • Exit test suite consumption loop when connector has stopped DBZ-6730

  • Update Quarkus to 3.2.3.Final DBZ-6740

  • Decouple Debezium Server and Extension Quarkus versions DBZ-6744

  • SingleProcessor remove redundant filter logic DBZ-6745

  • OracheSchemaMigrationIT fails after adding RAW data type support DBZ-6751

  • Missing or misspelled IDs result in downstream build errors DBZ-6754

  • Bump the MySQL binlog client version to 0.28.1 which includes significant GTID event performance improvements DBZ-6783

  • Add new Redis Sink connector parameter description to the documentation DBZ-6784

  • Upgrade Kafka to 3.5.1 DBZ-6785

Release 2.4.0.Alpha1 (July 14th 2023)

Kafka compatibility

This release has been built against Kafka Connect 3.5.0 and has been tested with version 3.5.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.4.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.4.0.Alpha1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.4.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

MongoDB connector interanlly used primary preferred hard-coded behaviour in certain scenarios. This is no longer the case and the connection string seting is used (DBZ-6521).

Vitess connector source info now contains the shard that was the source of the event (DBZ-6617).

New features

  • Capture & display critical connector metrics for Debezium UI DBZ-5321

  • Don’t require cluster-wide privileges when watching a single database/collection DBZ-6182

  • Debezium Offset-Editor example application DBZ-6338

  • Notify about initial snapshot progress DBZ-6416

  • Set Readpreference tags in the MongoDB client DBZ-6468

  • MySqlSnapshotChangeEventSource parallel execute createSchemaEventsForTables DBZ-6472

  • Refactor errors.max.retries to common connector framework DBZ-6573

  • Explain failure on existing publication update when switching to filtered from all_tables DBZ-6577

  • Debezium should honor read preference from connection string DBZ-6578

  • Document support for database restricted privileges for 2.4 DBZ-6592

  • Use source field in topic in table.format.name DBZ-6595

  • Support authentication with TC MongoDB deployments DBZ-6596

  • Support for getting primary key from header DBZ-6602

  • Support for custom tags in the connector metrics DBZ-6603

  • Update docs for new shard field DBZ-6627

  • Improve JDBC connector documentation DBZ-6632

  • Add configurable timeout to initialization procedure DBZ-6653

  • Introduce internal config option to control how close to CURRENT_SCN Oracle may mine DBZ-6660

  • Add support for XML_TYPE column type to Debezium connector for Oracle DBZ-3605

Fixes

  • Mysql connector fails to parse statement FLUSH FIREWALL_RULES DBZ-3925

  • Snapshot result not saved if LAST record is filtered out DBZ-5464

  • CloudEventsConverter throws static error on Kafka Connect 3.5+ DBZ-6517

  • Dependency io.debezium:debezium-testing-testcontainers affects logback in tests DBZ-6525

  • Batches with DELETE statement first will skip everything else DBZ-6576

  • Oracle unsupported DDL statement - drop multiple partitions DBZ-6585

  • Only Struct objects supported for [Header field insertion], found: null DBZ-6588

  • Support PostgreSQL coercion for UUID, JSON, and JSONB data types DBZ-6589

  • MySQL parser cannot parse CAST AS dec DBZ-6590

  • Excessive Log Message 'Marking Processed Record for Topic' DBZ-6597

  • Fixed DataCollections for table scan completion notificaiton DBZ-6605

  • Oracle connector is not recoverable if ORA-01327 is wrapped by another JDBC or Oracle exception DBZ-6610

  • Fatal error when parsing Mysql (Percona 5.7.39-42) procedure DBZ-6613

  • Build of Potgres connector fails when building against Kafka 2.X DBZ-6614

  • Upgrade postgresql driver to v42.6.0 DBZ-6619

  • MySQL ALTER USER with RETAIN CURRENT PASSWORD fails with parsing exception DBZ-6622

  • Inaccurate documentation regarding additional-condition DBZ-6628

  • Oracle connection SQLRecoverableExceptions are not retried by default DBZ-6633

  • Cannot delete non-null interval value DBZ-6648

  • ConcurrentModificationException thrown in Debezium 2.3 DBZ-6650

  • Dbz crashes on parsing Mysql Procedure Code (Statement Labels) DBZ-6651

  • CloudEvents converter is broken for JSON message deserialization DBZ-6654

  • Vitess: Connector fails if table name is a mysql reserved word DBZ-6656

  • Junit conflicts cause by test-containers module using transitive Junit5 from quarkus DBZ-6659

Other changes

  • Add the API endpoint to expose running connector metrics DBZ-5359

  • Display critical connector metrics DBZ-5360

  • Define and document schema history topic messages schema DBZ-5518

  • Align query.fetch.size across connectors DBZ-5676

  • Upgrade to Apache Kafka 3.5.0 DBZ-6047

  • Remove downstream related code from UI Frontend code DBZ-6394

  • Make Signal actions extensible DBZ-6417

  • Cleanup duplicit jobs from jenkins DBZ-6535

  • Implement sharded mongo ocp deployment and integration tests DBZ-6538

  • Refactor retry handling in Redis schema history DBZ-6594

  • Upgrade Quarkus to 3.2.0.Final DBZ-6626

  • Upgrade kcctl to 1.0.0.Beta3 DBZ-6642

  • Upgrade gRPC to 1.56.1 DBZ-6649

  • Disable Kafka 2.x CRON trigger DBZ-6667