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.7.Final (January 21st 2024)

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.3.7.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.7.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.3.7.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 DockerHub.

Breaking changes

There are no breaking changes in this release.

New features

There are no new features in this release.

Fixes

  • Oracle connector is ocasionally unable to find SCN DBZ-7345

Other changes

There are no other changes in this release.

Release 2.3.6.Final (January 12nd 2024)

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.3.6.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.6.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.3.6.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 DockerHub.

Breaking changes

There are no breaking changes in this release.

New features

There are no new features in this release.

Fixes

  • Connector frequently misses commit operations DBZ-6942

  • Missing events from Oracle 19c DBZ-6963

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

Other changes

There are no other changes in this release.

Release 2.3.5.Final (December 15th 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.3.5.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.5.Final plugin files, and restart the connector using the same configuration. Upon restart, the 2.3.5.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 DockerHub.

Breaking changes

There are no breaking changes in this release.

New features

There are no new features in this release.

Fixes

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

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

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

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

  • Single quote replication and loss of data DBZ-7006

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

  • [DBZ-6517] [HF] CloudEventsConverter throws static error on Kafka Connect 3.5+ DBZ-7263

Other changes

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

Release 2.3.4.Final (September 21st 2023)

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.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 DockerHub.

Breaking changes

There are no breaking changes in this release.

New features

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

Fixes

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

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

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

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

  • Clean log printout in Redis Debezium Sink DBZ-6908

  • 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

Other changes

  • 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.3.3.Final (September 4th 2023)

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

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

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

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

Fixes

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

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

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

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

  • Outbox transformation can cause connector to crash DBZ-6760

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

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

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

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

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

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

  • 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

  • Oracle test shouldContinueToUpdateOffsetsEvenWhenTableIsNotChanged fails with NPE DBZ-6860

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

Other changes

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

Release 2.3.2.Final (August 4th 2023)

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

Breaking changes

Oracle connector used 2000 as the default value for LogMiner query fetch size. The value was changed to 10000 based on community feedback as it provides significantly better performance without any negatives (DBZ-6729).

New features

There are no new features in this release.

Fixes

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

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

  • 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

  • SQL Server fail to start due to duplicate definition of query.fetch.size DBZ-6743

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

Other changes

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

  • Upstream documentation missing types for configurations DBZ-6707

  • Decouple Debezium Server and Extension Quarkus versions DBZ-6744

Release 2.3.1.Final (July 27th 2023)

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

Breaking changes

There are no breaking changes in this release.

New features

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

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

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

Fixes

  • 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

  • MySQL parser cannot parse CAST AS dec DBZ-6590

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

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

  • 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

  • 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

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

  • 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

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

  • 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

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

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

Other changes

  • Refactor retry handling in Redis schema history DBZ-6594

  • NotificationIT with Oracle xstream fails randomly DBZ-6672

  • Flaky Oracle test: shouldCaptureChangesForTransactionsAcrossSnapshotBoundaryWithoutReemittingDDLChanges DBZ-6673

Release 2.3.0.Final (June 20th 2023)

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

Breaking changes

There are no breaking changes in this release.

New features

  • Add support for custom SourceInfoStructMaker for adding new fields to source field DBZ-6076

  • Connector can potentially read a lot of sync topic messages on startup DBZ-6308

  • Allow to specify separate SID for rac.nodes settings DBZ-6359

  • Periodically clean up SGA using new LogMiner connection DBZ-6499

  • Upgrade debezium-connector-mysql tests to use MySQL 8 DBZ-6534

  • Remove duplicate partitions in TaskSyncContext. DBZ-6544

  • Support exactly-once semantic for streaming phase from Postgres connector DBZ-6547

  • Monitoring failed Incremental Snapshots DBZ-6552

Fixes

  • Upgrade to Infinispan 14.0.11.Final to fix CVE-2022-45047 DBZ-6193

  • Date and Time values without timezones are not persisted correctly based on database.time_zone DBZ-6399

  • "Ignoring invalid task provided offset" DBZ-6463

  • Oracle snapshot.include.collection.list should be prefixed with databaseName in documentation. DBZ-6474

  • Allow schema to be specified in the Debezium Sink Connector configuration DBZ-6491

  • Error value of negative seconds in convertOracleIntervalDaySecond DBZ-6513

  • Parse mysql table name failed which ending with backslash DBZ-6519

  • Oracle Connector: Snapshot fails with specific combination DBZ-6528

  • Table order is incorrect on snapshots DBZ-6533

  • Unhandled NullPointerException in PartitionRouting will crash the whole connect plugin DBZ-6543

  • Incorrect image name in postgres example of the operator repo DBZ-6548

  • Examples are not updated with correct image tags for released DBZ-6549

  • SQL grammar exception on MySQL ALTER statements with multiple columns DBZ-6554

  • debezium/connect image for 2.2.1.Final is not available on dockerhub or quay.io DBZ-6558

  • Bug in field.name.adjustment.mode Property DBZ-6559

  • Operator sets incorrect value of transformation.predicate when no predicate is specified DBZ-6560

  • Kubernetes-Config extension interferes with SSL tests due to k8 devservice starting up DBZ-6574

  • MySQL read-only connector with Kafka signals enabled fails on start up DBZ-6579

  • Redis schema history can fail upon startup DBZ-6580

Other changes

  • Use "debezium/kafka" container for Debezium UI tests instead of "confluentinc/cp-kafka" DBZ-6449

  • Include debezium operator in image build pipeline DBZ-6546

  • Update repository list in contributor list and missing commit workflows DBZ-6556

  • Upgrade MySQL JDBC driver to 8.0.33 DBZ-6563

  • Upgrade Google Cloud BOM to 26.17.0 DBZ-6570

Release 2.3.0.CR1 (June 9th 2023)

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

Breaking changes

There are no breaking changes in this release.

New features

  • Code Improvements for skip.messages.without.change DBZ-6366

  • Allow sending signals and receiving notifications via JMX DBZ-6424

  • MySql in debezium-parser-ddl does not support TABLE statement parsing DBZ-6435

  • Utilize event.processing.failure.handling.mode in Vitess replication connection DBZ-6510

  • Only use error processing mode on certain errors DBZ-6523

  • Use better hashing function for PartitionRouting DBZ-6529

  • Create PoC of Debezium Server Operator DBZ-6493

Fixes

  • Create OCP cluster provisioning jobs DBZ-3129

  • io.debezium.text.ParsingException: DDL statement couldn’t be parsed. Please open a Jira issue with the statement DBZ-6507

  • Oracle Connector failed parsing DDL Statement DBZ-6508

  • FileSignalChannel is not loaded DBZ-6509

  • MySqlReadOnlyIncrementalSnapshotChangeEventSource enforces Kafka dependency during initialization DBZ-6511

  • Debezium incremental snapshot chunk size documentation unclear or incorrect DBZ-6512

  • Debezium incremental snapshot chunk size documentation unclear or incorrect DBZ-6515

  • [PostgreSQL] LTree data is not being captured by streaming DBZ-6524

  • MySQL "national" keyword is not accepted as column name DBZ-6537

Other changes

  • Test Debezium on RED HAT OPENSHIFT DATABASE ACCESS - MongoDB Atlas DBZ-5231

  • Add docs on how to extend channels and notification DBZ-6408

  • Create Cron trigger for system tests DBZ-6423

  • Debezium UI Repo dependency update DBZ-6473

  • Add Debezium Server nightly images DBZ-6536

  • Include debezium operator in release scripts DBZ-6539

  • Start publishing nightly images for Debezium Operator DBZ-6541

  • Start releasing images for Debezium Operator DBZ-6542

Release 2.3.0.Beta1 (May 26th 2023)

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)

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