Release Notes for Debezium 1.0

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

Release 1.0.0.Beta3 (November 14th, 2019)

Kafka compatibility

This release has been built against Kafka Connect 2.3.1 and has been tested with version 2.3.1 of the Kafka brokers. See the Kafka documentation for compatibility with other versions of Kafka brokers.

Upgrading

Before upgrading the MySQL, MongoDB, PostgreSQL or SQL Server connectors, 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.0.0.Beta3 from any of the earlier 1.0.x, 0.10.x, 0.9.x, 0.8.x, 0.7.x, 0.6.x, 0.5.x, 0.4.x, 0.3.x, 0.2.x, or 0.1.x versions, first check the upgrading notes for the version you’re using. Gracefully stop the running connector, remove the old plugin files, install the 1.0.0.Beta3 plugin files, and restart the connector using the same configuration. Upon restart, the 1.0.0.Beta3 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

Configuration parameter drop_on_stop of POstgreSQL connector has been renamed to drop.on.stop (DBZ-1595) to make it consistent with other parameter names.

New Features

  • Standardize source info for Cassandra connector DBZ-1408

  • Clarify presence of old values when not using REPLICA IDENTITY FULL DBZ-1518

  • Propagate replicator exception so failure reason is available from Connect DBZ-1583

  • Envelope methods should accept Instant instead of long for "ts" parameter DBZ-1607

Fixes

This release includes the following fixes:

  • Debezium Erroneously Reporting No Tables to Capture DBZ-1519

  • Debezium Oracle connector attempting to analyze tables DBZ-1569

  • Null values in "before" are populated with "__debezium_unavailable_value" DBZ-1570

  • Postgresql 11+ pgoutput plugin error with truncate DBZ-1576

  • Regression of postgres Connector times out in schema discovery for DBs with many tables DBZ-1579

  • The ts_ms value is not correct during the snapshot processing DBZ-1588

  • LogInterceptor is not thread-safe DBZ-1590

  • Heartbeats are not generated for non-whitelisted tables DBZ-1592

  • Config tombstones.on.delete is missing from SQL Server Connector configDef DBZ-1593

  • AWS RDS Performance Insights screwed a little by non-closed statement in "SELECT COUNT(1) FROM pg_publication" DBZ-1596

  • Update Postgres documentation to use ts_ms instead of ts_usec DBZ-1610

  • Exception while trying snapshot schema of non-whitelisted table DBZ-1613

Other changes

This release includes also other changes:

  • Auto-format source code upon build DBZ-1392

  • Update documentation based on Technology Preview DBZ-1543

  • Reduce size of Postgres container images DBZ-1549

  • Debezium should not use SHARE UPDATE EXCLUSIVE MODE locks DBZ-1559

  • Allows tags to be passed to CI jobs DBZ-1578

  • Upgrade MongoDB driver to 3.11 DBZ-1597

  • Run formatter validation in Travis CI DBZ-1603

  • Place formatting rules into Maven module DBZ-1605

  • Upgrade to Kafka 2.3.1 DBZ-1612

  • Allow per-connector setting for schema/catalog precedence in TableId use DBZ-1555

Release 1.0.0.Beta2 (October 24th, 2019)

Kafka compatibility

This release has been built against Kafka Connect 2.3.0 and has been tested with version 2.3.0 of the Kafka brokers. See the Kafka documentation for compatibility with other versions of Kafka brokers.

Upgrading

Before upgrading the MySQL, MongoDB, PostgreSQL or SQL Server connectors, 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.0.0.Beta2 from any of the earlier 1.0.x, 0.10.x, 0.9.x, 0.8.x, 0.7.x, 0.6.x, 0.5.x, 0.4.x, 0.3.x, 0.2.x, or 0.1.x versions, first check the upgrading notes for the version you’re using. Gracefully stop the running connector, remove the old plugin files, install the 1.0.0.Beta2 plugin files, and restart the connector using the same configuration. Upon restart, the 1.0.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 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

  • Update tooling image to use latest kafkacat DBZ-1522

  • Validate configured replication slot names DBZ-1525

  • Make password field to be hidden for MS SQL connector DBZ-1554

  • Raise a warning about growing backlog DBZ-1565

  • Support Postgres LTREE columns DBZ-1336

Fixes

This release includes the following fixes:

  • Aborting snapshot due to error when last running 'UNLOCK TABLES': Only REPEATABLE READ isolation level is supported for START TRANSACTION WITH CONSISTENT SNAPSHOT in RocksDB Storage Engine. DBZ-1428

  • MySQL Connector fails to parse DDL containing the keyword VISIBLE for index definitions DBZ-1534

  • MySQL connector fails to parse DDL - GRANT SESSION_VARIABLES_ADMIN…​ DBZ-1535

  • Mysql connector: The primary key cannot reference a non-existant column 'id' in table '*' DBZ-1560

  • Incorrect source struct’s collection field when dot is present in collection name DBZ-1563

  • Transaction left open after db snapshot DBZ-1564

Other changes

This release includes also other changes:

  • Add Postgres 12 to testing matrix DBZ-1542

  • Update Katacoda learning experience DBZ-1548

Release 1.0.0.Beta1 (October 17th, 2019)

Kafka compatibility

This release has been built against Kafka Connect 2.3.0 and has been tested with version 2.3.0 of the Kafka brokers. See the Kafka documentation for compatibility with other versions of Kafka brokers.

Upgrading

Before upgrading the MySQL, MongoDB, PostgreSQL or SQL Server connectors, 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.0.0.Beta1 from any of the earlier 0.10.x, 0.9.x, 0.8.x, 0.7.x, 0.6.x, 0.5.x, 0.4.x, 0.3.x, 0.2.x, or 0.1.x versions, first check the upgrading notes for the version you’re using. Gracefully stop the running connector, remove the old plugin files, install the 1.0.0.Beta1 plugin files, and restart the connector using the same configuration. Upon restart, the 1.0.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

The ExtractNewDocumentState and EventRouter SMTs now propagate any heartbeat or schema change messages unchanged instead of dropping them as before. This is to ensure consistency with the ExtractNewRecordState SMT (DBZ-1513).

The new Postgres connector option interval.handling.mode allows to control whether INTERVAL columns should be exported as microseconds (previous behavior, remains the default) or as ISO 8601 formatted string (DBZ-1498). The following upgrade order must be maintained when existing connectors capture INTERVAL columns:

  1. Upgrade the Debezium Kafka Connect Postgres connector

  2. Upgrade the logical decoding plug-in installed in the database

  3. (Optionally) switch interval.handling.mode to string

In particular it should be avoided to upgrade the logical decoding plug-in before the connector, as this will cause no value to be exported for INTERVAL columns.

New Features

  • Provide alternative mapping for INTERVAL DBZ-1498

  • Ensure message keys have correct field order DBZ-1507

  • Image incorrect on Deploying Debezium on OpenShift DBZ-1545

  • Indicate table locking issues in log DBZ-1280

Fixes

This release includes the following fixes:

  • Debezium fails to snapshot large databases DBZ-685

  • Connector Postgres runs out of disk space DBZ-892

  • Debezium-MySQL Connector Fails while parsing AWS RDS internal events DBZ-1492

  • MongoDB ExtractNewDocumentState SMT blocks heartbeat messages DBZ-1513

  • pgoutput string decoding depends on JVM default charset DBZ-1532

  • Whitespaces not stripped from table.whitelist DBZ-1546

Other changes

This release includes also other changes:

  • Upgrade to latest JBoss Parent POM DBZ-675

  • CheckStyle: Flag missing whitespace DBZ-1341

  • Upgrade to the latest Checkstyle plugin DBZ-1355

  • CheckStyle: no code after closing braces DBZ-1391

  • Add "adopters" file DBZ-1460

  • Add Google Analytics to Antora-published pages DBZ-1526

  • Create 0.10 RPM for postgres-decoderbufs DBZ-1540

  • Postgres documentation fixes DBZ-1544

back to top