Release Notes for Debezium 1.4

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

Release 1.4.0.Alpha2 (November 16th, 2020)

Kafka compatibility

This release has been built against Kafka Connect 2.6.0 and has been tested with version 2.6.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 1.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 1.4.0.Alpha2 plugin files, and restart the connector using the same configuration. Upon restart, the 1.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in this release.

New Features

  • Move testcontainers changes on DebeziumContainer from UI PoC backend to Debezium main repo DBZ-2602

  • Add ability to map new name for the fields and headers DBZ-2606

  • Add close call to the Snapshotter interface DBZ-2608

  • Overriding Character Set Mapping DBZ-2673

  • Support PostgreSQL connector retry when database is restarted DBZ-2685

  • Cassandra connector documentation typos DBZ-2701

  • Fix typo in converters doc DBZ-2717

  • Add tests for DBZ-2617: PG connector does not enter FAILED state on failing heartbeats DBZ-2724

  • DBZ-2662 Control ChangeEventQueue by the size in bytes DBZ-2662

Fixes

  • Oracle throw "no snapshot found based on specified time" when running flashback query DBZ-1446

  • Exception when PK definition precedes column definition DBZ-2580

  • Patroni can’t stop PostgreSQL when Debezium is streaming DBZ-2617

  • ChangeRecord informations don’t connect with the TableSchema DBZ-2679

  • MySQL connector fails on a zero date DBZ-2682

  • Oracle LogMiner doesn’t support partition tables DBZ-2683

  • DB2 doesn’t start reliably in OCP DBZ-2693

  • Dropped columns cause NPE in SqlServerConnector DBZ-2716

  • Timestamp default value in 'yyyy-mm-dd' format fails MySQL connector DBZ-2726

  • Connection timeout on write should retry DBZ-2727

  • No viable alternative at input error on "min" column DBZ-2738

  • SQLServer CI error in SqlServerConnectorIT.whenCaptureInstanceExcludesColumnsAndColumnsRenamedExpectNoErrors:1473 DBZ-2747

  • debezium-connector-db2: DB2 SQL Error: SQLCODE=-206 on DB2 for z/OS DBZ-2755

  • no viable alternative at input 'alter table order drop CONSTRAINT' DBZ-2760

  • Tests are failing on macos DBZ-2762

Other changes

  • Move CI to Github Actions for all repositories DBZ-1720

  • Privileges missing from setup in documentation - Oracle LogMiner connector DBZ-2628

  • Add validation that replication slot doesn’t exist DBZ-2637

  • Update OpenJDK Quality Outreach jobs DBZ-2638

  • Re-unify monitoring content in the operations/monitoring.adoc file DBZ-2659

  • Pull oracle specific changes for reading table column metadata into debezium-core DBZ-2690

  • Intermittent test failure on CI - PostgresConnectorIT#shouldRegularlyFlushLsnWithTxMonitoring DBZ-2704

  • Topic routing doc formatting fix DBZ-2708

  • Re-unify logging content in the operations/logging.adoc file DBZ-2721

  • Incorporate Oracle LogMiner implementation updates DBZ-2729

  • Upgrade Vitess docker image to Vitess 8.0.0 DBZ-2749

  • Intermittent SQL Server test failure on CI - SqlServerConnectorIT DBZ-2625

  • Change initial.sync.max.threads to snapshot.max.threads DBZ-2742

Release 1.4.0.Alpha1 (October 22nd, 2020)

Kafka compatibility

This release has been built against Kafka Connect 2.6.0 and has been tested with version 2.6.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 1.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 1.4.0.Alpha1 plugin files, and restart the connector using the same configuration. Upon restart, the 1.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in this release.

New Features

  • Allow to specify subset of captured tables to be snapshotted DBZ-2456

  • Implement snapshot select override behavior for MongoDB DBZ-2496

  • Asciidoc block titles are rendered the same as regular text DBZ-2631

  • Allow closing of hung JDBC connection DBZ-2632

  • Hide stacktrace when default value for SQL Server cannot be parsed DBZ-2642

  • Implement a CDC connector for Vitess DBZ-2463

  • SqlServer - Skip processing of LSNs not associated with change table entries. DBZ-2582

Fixes

  • Cant override environment variables DBZ-2559

  • Inconsistencies in PostgreSQL Connector Docs DBZ-2584

  • ConcurrentModificationException during exporting data for a mongodb collection in a sharded cluster DBZ-2597

  • Mysql connector didn’t pass the default db charset to the column definition DBZ-2604

  • [Doc] "registry.redhat.io/amq7/amq-streams-kafka-25: unknown: Not Found" error occurs DBZ-2609

  • [Doc] "Error: no context directory and no Containerfile specified" error occurs DBZ-2610

  • SqlExceptions using dbz with Oracle on RDS online logs and logminer DBZ-2624

  • Mining session stopped - task killed/SQL operation cancelled - Oracle LogMiner DBZ-2629

  • Unparseable DDL: Using 'trigger' as table alias in view creation DBZ-2639

  • Antlr DDL parser fails to interpret BLOB([size]) DBZ-2641

  • MySQL Connector keeps stale offset metadata after snapshot.new.tables is changed DBZ-2643

  • WAL logs are not flushed in Postgres Connector DBZ-2653

  • Debezium server Event Hubs plugin support in v1.3 DBZ-2660

  • Cassandra Connector doesn’t use log4j for logging correctly DBZ-2661

  • Should Allow NonAsciiCharacter in SQL DBZ-2670

  • MariaDB nextval function is not supported in grammar DBZ-2671

  • Sanitize field name do not santize sub struct field DBZ-2680

  • Debezium fails if a non-existing view with the same name as existing table is dropped DBZ-2688

Other changes

  • Merge MySQL doc source files into one again DBZ-2127

  • Metrics links duplicate anchor IDs DBZ-2497

  • Slim down Vitess container image DBZ-2551

  • Modify release peipeline to support per-connector repos e.g. Vitess DBZ-2611

  • Add Vitess connector to Kafka Connect container image DBZ-2618

  • User Guide Documentation corrections for PostgreSQL DBZ-2621

  • Checkstyle should be built as a part of GH check formatting action DBZ-2623

  • Upgrade MySQL JDBC driver to version 8.0.19 DBZ-2626

  • Add support for multiple shard GTIDs in VGTID DBZ-2635

  • Add documentation for Vitess connector DBZ-2645

  • Restrict matrix job configurations to run only on Slaves DBZ-2648

  • Upgrade JUnit to 4.13.1 DBZ-2658

  • Avoid parsing generated files in Checkstyle DBZ-2669

  • Update debezium/awestruct image to use Antora 2.3.4 DBZ-2674

  • Fix doc typos and minor format glitches for downstream rendering DBZ-2681

  • Intermittent test failure on CI - RecordsStreamProducerIT#shouldReceiveHeartbeatAlsoWhenChangingNonWhitelistedTable() DBZ-2344

back to top