1. Releases
  2. 2.3
  3. Release Notes for Debezium 2.3

Release Notes for Debezium 2.3

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

Release 2.3.0.Beta1 (May 26th 2023)

See the 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 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.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.3.0.Beta1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.3.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 DockerHub.

Breaking changes

JDBC storage was by default using UTF-16 encoding. Most of the databases use UTF-8 as the default so JDBC storage was aligned with it (DBZ-6476).

New features

  • Testsuite should deploy PostgreSQL with Primary-Secondary streaming replication DBZ-3202

  • PostgreSQL: Set Replica Identity when the connector starts DBZ-6112

  • Correlate incremental snapshot notifications ids with execute signal DBZ-6447

  • [MariaDB] Add support for userstat plugin keywords DBZ-6459

  • Add a header provider string DBZ-6489

Fixes

  • Debezium Server stops sending events to Google Cloud Pub/Sub DBZ-5175

  • Snapshot step 5 - Reading structure of captured tables time too long DBZ-6439

  • Oracle parallel snapshots do not properly set PDB context when using multitenancy DBZ-6457

  • Debezium Server cannot recover from Google Pub/Sub errors DBZ-6461

  • DDL statement couldn’t be parsed: AUTHENTICATION_POLICY_ADMIN DBZ-6479

  • Db2 connector can fail with NPE on notification sending DBZ-6485

  • BigDecimal fails when queue memory size limit is in place DBZ-6490

  • ORACLE table can not be captrued, got runtime.NoViableAltException DBZ-6492

  • Signal poll interval has incorrect default value DBZ-6496

  • Oracle JDBC driver 23.x throws ORA-18716 - not in any time zone DBZ-6502

  • Alpine postgres images should use llvm/clang 15 explicitly DBZ-6506

  • ExtractNewRecordState SMT in combination with HeaderToValue SMT results in Unexpected field name exception DBZ-6486

Other changes

  • Verify MongoDB Connector with AWS DocumentDB DBZ-6419

  • Enable set log level in tests DBZ-6460

  • Check OOME on CI tests DBZ-6462

  • Signaling data collection document should refer to source database DBZ-6470

Release 2.3.0.Alpha1 (May 11st 2023)

See the 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 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.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.3.0.Alpha1 plugin files, and restart the connector using the same configuration. Upon restart, the 2.3.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 DockerHub.

Breaking changes

MySQL connector now uses SSL connection if available by default (DBZ-6340).

New features

  • Enable Debezium to send notifications about it’s status DBZ-1973

  • Saving Debezium states to JDBC database DBZ-3621

  • Make signalling channel configurable DBZ-4027

  • Edit a connector in Debezium UI DBZ-5313

  • Add connector display name and id to Config endpoint response DBZ-5865

  • Introduce LogMiner query filtering modes DBZ-6254

  • Ensure that the connector can start from a stale timestamp more than one hour into the past DBZ-6307

  • Add JWT authentication to HTTP Client DBZ-6348

  • Monitoring progress of Incremental Snapshots DBZ-6354

  • log.mining.transaction.retention.hours should reference last offset and not sysdate DBZ-6355

  • Support multiple tasks when streaming shard list DBZ-6365

  • Kinesis Sink - AWS Credentials Provider DBZ-6372

  • Fix existing bug in information schema query in the Spanner connector DBZ-6385

  • change logging level of skip.messages.without.change DBZ-6391

  • Debezium UI should ignore unsupported connectors, including unsupported Debezium connectors DBZ-6426

  • Make DELETE sql configurable in JDBC Storage DBZ-6433

  • Include redo/archive log metadata on ORA-01291 exceptions DBZ-6436

Fixes

  • Back button is not working on the review page UI DBZ-5841

  • Toasted varying character array and date array are not correcly processed DBZ-6122

  • Incorrect dependencies in Debezium Server for Cassandra connector DBZ-6147

  • Lock contention on LOG_MINING_FLUSH table when multiple connectors deployed DBZ-6256

  • Document Requirements for multiple connectors on same db host DBZ-6321

  • The rs_id field is null in Oracle change event source information block DBZ-6329

  • Using pg_replication_slot_advance which is not supported by PostgreSQL10. DBZ-6353

  • 'CREATE TABLE t (c NATIONAL CHAR)' parsing failed DBZ-6357

  • Toasted hstore are not correcly processed DBZ-6379

  • Snapshotting does not work for hstore in Map mode DBZ-6384

  • Oracle DDL shrink space for table partition can not be parsed DBZ-6386

  • __source_ts_ms r (read) operation date is set to future for SQL Server DBZ-6388

  • Connector cards are misaligned on first step DBZ-6392

  • Debezium Server snapshots are not published DBZ-6395

  • PostgreSQL connector task fails to resume streaming because replication slot is active DBZ-6396

  • MySql in debezium-parser-ddl :The inserted sql statement reports an error DBZ-6401

  • MongoDB connector crashes on invalid resume token DBZ-6402

  • Set (instead of adding) Authorization Headers DBZ-6405

  • New SMT HeaderToValue not working DBZ-6411

  • Debezium Server 2.2.0.Final BOM refers to debezium-build-parent 2.2.0-SNAPSHOT DBZ-6437

  • NPE on read-only MySQL connector start up DBZ-6440

  • Oracle Connector failed parsing DDL Statement DBZ-6442

  • Oracle DDL shrink space for index partition can not be parsed DBZ-6446

Other changes

  • Verify streaming off of secondary works DBZ-1661

  • Remove the old connector type endpoints from the UI backend DBZ-5604

  • Incremental snapshot completion notifications DBZ-5632

  • Change connector test matrix jobs to pipeline jobs and migrate them to gitlab jenkins DBZ-5861

  • Add Debezium steps when performing a PostgreSQL database upgrade DBZ-6046

  • Test migration from Debezium 1.x to 2.x DBZ-6126

  • Remove OCP 4.8 and 4.9 from 1.x supported configurations page DBZ-6132

  • Remove potentially dangerous JDBC props in MySQL connections DBZ-6157

  • Refactor storage implementations DBZ-6209

  • Align connector field snapshot.mode descriptions as per documentation DBZ-6259

  • Document "incubating" status of incremental snapshot for sharded MongoDB clusters DBZ-6342

  • Run debezium-connector-jdbc build on 'Build Debezium' CI workflow DBZ-6360

  • Migrate Debezium UI MongoDB to MongoDbReplicaSet from core DBZ-6363

  • Base the "replaceable" build numbers in legacy deployment instructions on debezium-build-number attribute DBZ-6371

  • Align Debezium UI to Debezium 2.3 DBZ-6406

  • Fix CORS error in UI due to Quarkus 3 upgrade DBZ-6422

  • Improve debezium-storage CI build step DBZ-6443

  • Use debezium-bom versions for shared dependencies in Debezium UI DBZ-6453