1. Releases
  2. 1.6
  3. Debezium 1.6发行说明开云体育官方注册网址

Debezium 1.6发行说明开云体育官方注册网址

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

Release 1.6.4.Final(December 1st, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.1 and has been tested with version 2.7.1 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.4.Final plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

There are no new features in the releases.

Fixes

  • OracleSchemaMigrationIT#shouldNotEmitDdlEventsForNonTableObjects fails for XstreamDBZ-4186

  • DML statement couldn’t be parsedDBZ-4194

  • Debezium log miner processes get terminated with ORA-04030 error in idle database environment.DBZ-4204

  • io.debezium.text.ParsingException: DDL statement couldn’t be parsed. Please open a Jira issue with the statement 'DROP TABLE IF EXISTS condition'DBZ-4210

  • DDL statement couldn’t be parsedDBZ-4224

  • CHAR / NCHAR precision is not correctly derived from DDL statementsDBZ-4233

  • RelationalChangeRecordEmitter calls "LoggerFactory.getLogger(getClass())" for each instance of the emitterDBZ-4309

Other changes

  • Document incremental chunk size settingDBZ-4127

  • Missing documentation for max.iteration.transactions optionDBZ-4129

  • Upgrade MySQL JDBC driver to 8.0.27DBZ-4286

Release 1.6.3.Final(2021年10月21日)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.1 and has been tested with version 2.7.1 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.3.Final plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

  • Oracle - Provide a more user-friendly way to update SCNDBZ-3876

Fixes

  • Status stays in RUNNING for Postgres Connector after Postgres is stoppedDBZ-3655

  • Oracle connector unable to start in archive only modeDBZ-3712

  • Row hashing in LogMiner Query not able to differentiate between rows of a statement.DBZ-3834

  • The chunk select statement is incorrect for combined primary key in incremental snapshotDBZ-3860

  • DML statement couldn’t be parsedDBZ-3892

  • Oracle Connector replicating data from all PDBs. Missing PDB filter during replication.DBZ-3954

  • Oracle connector Parsing Exception: DDL statement couldn’t be parsedDBZ-3962

  • Oracle-Connector fails parsing a DDL statementDBZ-3977

  • Oracle connector fails after error ORA-01327DBZ-4010

  • Incorrect incremental snapshot DDL triggers snapshot that generates unending* inserts against signalling tableDBZ-4013

  • Oracle-Connector fails parsing a DDL statement (truncate partition)DBZ-4017

  • DDL statement couldn’t be parsedDBZ-4026

  • Question about handling Raw column typesDBZ-4037

  • Incremental snapshotting of a table can be prematurely terminated after restartDBZ-4057

  • Events are missed with Oracle connector due to LGWR buffer not being flushed to redo logsDBZ-4067

  • Database history is constantly being reconfiguredDBZ-4106

  • Debezium deals with Oracle DDL appeared IndexOutOfBoundsException: Index: 0, Size: 0DBZ-4135

  • Possible OutOfMemoryError with tracking schema changesDBZ-4151

  • DDL ParsingException - not all table compression modes are supportedDBZ-4158

Other changes

  • Hyper-link references between options in the Outbox SMT options tableDBZ-3920

  • Incorrect documentation for message.key.columnsDBZ-3437

  • Promote Outbox SMT to GADBZ-3584

  • Upgrade to binlog-client 0.25.3DBZ-3787

  • Document awareness of Oracle database tuningDBZ-3880

  • Update antora.yml file with new values for SMT attributesDBZ-3922

  • Add top-level Transformation menu node for downstream docsDBZ-3931

  • Update docs to specify that connectors track metadata only for transactions that occur after deploymentDBZ-3961

  • RemoveGRANT ALTER ANY TABLEfrom Oracle documentationDBZ-4007

  • Misc. MongoDB connector docs fixesDBZ-4149

Release 1.6.2.Final(September 2nd, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.1 and has been tested with version 2.7.1 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.2.Final plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

There are no new features in the release.

Fixes

  • 失效链接路由器docum Avro和发件箱的事件entationDBZ-3430

  • Oracle LogMiner DdlParser ErrorDBZ-3723

  • DDL statement couldn’t be parsedDBZ-3755

  • Debezium Oracle connector stops with DDL parsing errorDBZ-3759

  • Debezium snapshot.select.statement.overrides overrides not usedDBZ-3760

  • Server name pattern is unnecessarily restrictive.DBZ-3765

  • Exception thrown from getTableColumnsFromDatabaseDBZ-3769

  • Crash when processing MySQL 5.7.28 TIME fields returns empty blob instead of nullDBZ-3773

  • Add DEFAULT to partition option engineDBZ-3784

  • Initiating MongoDB connector causes oplog table scanDBZ-3788

  • SRCFG00014: The config property debezium.sink.pravega.scope is required but it could not be found in any config sourceDBZ-3792

  • Debezium 1.6.1 expecting database.port even when database.url is provided in config.DBZ-3813

  • Postgres numeric default value throwing exceptionDBZ-3816

  • Snapshot locking mode "minimal_percona" incorrectly resets transaction & isolation stateDBZ-3838

  • Typo with prodname asciidoc attribute usageDBZ-3856

  • Oracle unparsable DDL issueDBZ-3877

  • Support AS clause in GRANT statementDBZ-3878

  • Error Parsing Oracle DDL dropping PKDBZ-3886

  • EMPTY_CLOB() and EMPTY_BLOB() should be treated as empty LOB valuesDBZ-3893

  • Oracle DDL parsing issueDBZ-3896

  • DEBEZIUM producer stops unexpectedly trying to change column in table which does not existDBZ-3898

  • "binary.handling.mode": "hex" setting works incorrectly for values with trailing zerosDBZ-3912

  • Incorrect validation of truncate handling modeDBZ-3935

Other changes

  • Discuss SMT predicates in docsDBZ-3227

  • Adjust to changed Strimzi CRDsDBZ-3385

  • Clarify lifecycle of snapshot metricsDBZ-3613

  • Error in description of the property column.mask.hash.hashAlgorithm.with.salt.saltDBZ-3802

  • Improperly constructed links generating downstream build errorsDBZ-3858

  • Extract new top-level menu node for SMTsDBZ-3873

  • Upgrade to Jackson Databind version 2.10.5.1DBZ-3927

  • Upgrade ZooKeeper in 1.6 container imageDBZ-3950

  • Upgrade Kafka container image to 2.7.1DBZ-3956

  • Performance issue due to inefficient ObjectMapper initializationDBZ-3770

Release 1.6.1.Final(July 23rd, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.1.Final plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

There are no new features in the release.

Fixes

  • Support invisible columns with MySql 8.0.23+DBZ-3623

  • Db2Connector is unable to establish validation connectionDBZ-3632

  • MySQL Connector error after execute a "create role" statementDBZ-3686

  • Error parsing query, even with database.history.skip.unparseable.ddlDBZ-3717

  • Support for TABLE_TYPE missing form MySQL grammarDBZ-3718

  • Debezium mysql connector plugin throws SQL syntax error during incremental snapshotDBZ-3725

Other changes

  • Add documentation about new capturing implementation for the MySQL connector to downstream productDBZ-3140

  • Doc clarification on connector rewriteDBZ-3711

  • Update Oracle connector deployment instructions for consistencyDBZ-3772

Release 1.6.0.Final(June 30th, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.0.Final plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

  • Allow specifying of Oracle archive log locationDBZ-3661

Fixes

  • Fix connect container build to be compatible with Oracle Instant ClientDBZ-2547

  • Schema change events of excluded databases are discardedDBZ-3622

  • Provide a descriptive error when enabling log.mining.archive.log.only.mode with an offset SCN that isn’t yet in an archive log.DBZ-3665

  • When LOB support is disabled, use legacy SCN mining algorithmDBZ-3676

Other changes

  • Oracle connector error with tables using unique index keys: "key must not be null"DBZ-1211

  • Database history properties missing in connector docsDBZ-3459

  • Oracle connector doc fixesDBZ-3662

  • 改变reached max batch size log message to DEBUG levelDBZ-3664

  • Remove unused codeDBZ-3672

  • Update deprecated config for debezium smtDBZ-3673

  • Align Antlr versions used during testingDBZ-3675

Release 1.6.0.CR1(June 24th, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.0.CR1 plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 docker images then do not forget to pull them fresh from Docker registry.

Breaking changes

There are no breaking changes in the release.

New Features

  • Implement SKIPPED_OPERATIONS for SQLServerDBZ-2697

  • Handling database connection timeout during schema recoveryDBZ-3615

  • Scope mined DDL events to include/exclude lists if providedDBZ-3634

  • Support heartbeats during periods of low change event activityDBZ-3639

Fixes

  • Fix exception on not found tableDBZ-3523

  • Transaction commit event dispatch fails if no active transaction in progress.DBZ-3593

  • Additional unique index referencing columns not exposed by CDC causes exceptionDBZ-3597

  • GRANT/REVOKE for roles is not workingDBZ-3610

  • ParsingException for ALTER TABLE against a table that is unknown to the connector.DBZ-3612

  • Oracle connector continually logging warnings about already processed transactions.DBZ-3616

  • StringIndexOutOfBoundsException thrown while handling UTF-8 charactersDBZ-3618

  • DDL ParsingException - "SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS"DBZ-3619

  • Oracle transaction reconciliation fails to lookup primary key columns if UPDATE sets columns to only NULLDBZ-3631

  • Oracle DDL parser fails on CREATE TABLE: mismatched input 'maxtrans' expecting {'AS', ';'}DBZ-3641

  • Antlr version mismatchDBZ-3646

  • SQL Agent does not start in SqlServer image when deployed to openshiftDBZ-3648

  • Java UBI image is lacking gzip utilityDBZ-3659

Other changes

  • Upgrade to Apicurio Registry 2.0DBZ-3171

  • Vitess: rename "master" branch to "main"dbz - 3275

  • Formatting updates to correct errors in documentation buildsDBZ-3518

  • Prepare test-suite for Kafka on RHELDBZ-3566

  • Upgrade to Quarkus 2.0.0.FinalDBZ-3602

  • Some dependencies are broken in ocp testsuite after BOM introductionDBZ-3625

  • Handle updated json schema for connector passwordsDBZ-3637

  • MySQL SourceInfo should be publicDBZ-3638

  • Change CLOB/BLOB data type support to an opt-in featureDBZ-3645

  • Denote BLOB support as incubatingDBZ-3651

Release 1.6.0.Beta2(June 10th, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.0.Beta2 plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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 the release.

New Features

  • Clarification on MySQL vs MariaDb UsageDBZ-1145

  • Pravega sink for Debezium ServerDBZ-3546

  • Postgres - Column default values are not extractedDBZ-2790

  • Add support for snapshot.include.collection.listDBZ-3062

  • Apply filters with empty filter changes 'Exclude' selection to 'Include'DBZ-3102

  • Adjust OpenShift tests to support new version of Strimzi CRDsDBZ-3475

  • Remove SchemaProcessor From Cassandra ConnectorDBZ-3506

  • Provide asnapshot.locking.modeoption for OracleDBZ-3557

  • Implement support for JSON function in MySQL parserDBZ-3559

Fixes

  • AbstractConnectorTest should work in environment with longer latencyDBZ-400

  • PostgreSQL connector task fails to resume streaming because replication slot is activeDBZ-3068

  • SQL Server connector buffers all CDC events in memory if more than one table is capturedDBZ-3486

  • SQLServer low throughput tables increase usage of TempDBDBZ-3515

  • Incorrectly identifies primary member of replica setDBZ-3522

  • Cannot enable binlog streaming when INITIAL_ONLY snapshot mode configuredDBZ-3529

  • Connector CRD name and database.server.name cannot use the same value in OCP test-suiteDBZ-3538

  • SelectLobParser checks for lowercase "is null" instead of uppercase "IS NULL"DBZ-3545

  • DDL ParsingException "mismatched input 'sharing'" for create table syntax.DBZ-3549

  • DDL ParsingException on alter tableDBZ-3554

  • ORA-00310 when online redo log is archived and replaced by redo log with new sequenceDBZ-3561

  • Server name pattern is unnecessarily restrictiveDBZ-3562

  • ORA-01289 error encountered on Oracle RAC when multiple logs are mined with same sequence numberDBZ-3563

  • MySQL metrics documentation refers to legacy implementationDBZ-3572

  • Update downstream MySQL doc to reference streaming metrics vs. binlog metricsDBZ-3582

  • No viable alternative at input "add COLUMN optional"DBZ-3586

  • NPE when OracleValueConverters get unsupported jdbc typeDBZ-3587

  • SelectLobParser throws NullPointerException when parsing SQL for an unknown tableDBZ-3591

  • Pulsar sink tries to convert null key to stringDBZ-3595

  • Oracle RAC URL does not correctly substitute node IP addressesDBZ-3599

  • Oracle Connector - got InputMismatchException mismatched input 'CASCADE' expecting {'AS', 'PURGE', ';'}DBZ-3606

Other changes

  • Unsupported column types should be ignored as with other connectorsDBZ-814

  • Make outbox extensions dependency on tracing extension optionalDBZ-2834

  • Avoid copying in DML handlingDBZ-3328

  • Document impact of using --hostname when starting Connect containerDBZ-3466

  • Update external link to AMQ Streams documentationDBZ-3502

  • Update external links in downstream docs to AMQ Streams deployment informationDBZ-3525

  • Debezium Server Core builds plugin artifactDBZ-3542

  • List contributors script fails when name contains a "/" characterDBZ-3544

  • Upgrade to Quarkus 2.0.0.CR3DBZ-3550

  • Reduce DB round-trips for LOB handlingDBZ-3556

  • Oracle benchmark does not execute LogMiner parser performance testsDBZ-3560

  • Clarify purpose of database.history.retention.hoursDBZ-3565

  • Improve documentation related to signalling table DDLDBZ-3568

  • cassandra-driver-core 3.5.0 managed in Debezium BOM too old for testcontainers 1.15.3DBZ-3589

  • Remove some dead code in Postgres connectorDBZ-3596

  • Debezium server sink oracle database to pulsar without default namespace "public/default"DBZ-3601

  • Document OffsetContext.incrementalSnapshotEvents()DBZ-3607

  • Database skipping logic isn’t correctDBZ-3608

Release 1.6.0.Beta1(May 20th, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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 1.6.0.Beta1 plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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

RENAME TABLEstatement with multiple tables now emits multiple schema change events, one for each of the renamed tables (DBZ-3399).

New Features

  • Support ad hoc snapshots on MySQL connectorDBZ-66

  • Support DDL operationsDBZ-2916

  • Add support for RAW, LONG, LONG RAW, BLOB, and CLOB data typesDBZ-2948

  • Update Doc For Cassandra ConnectorDBZ-3092

  • Document log.mining.strategy for Oracle connectorDBZ-3393

  • Update DOC with the new NUM_OF_CHANGE_EVENT_QUEUES parameterDBZ-3480

  • Use date format model that does not depend on client NLS settings in integration testsDBZ-3482

  • Provide Japanese translation of README.mdDBZ-3503

  • Better handling of invalid SQL Server connector configurationDBZ-3505

  • Allow table.include.list and table.exclude.list to be updated after a connector is createdDBZ-1263

  • Allow retry when SQL Server is down temporarilyDBZ-3339

Fixes

  • Database name should not be converted to lower case if tablenameCaseInsensitive=True in Oracle ConnectorDBZ-2203

  • Not able to configure Debezium Server via smallrye/microprofile environment variablesDBZ-2622

  • Upgrading from debezium 1.2.2 to 1.4.0 stopped snapshotting new tablesDBZ-2944

  • oracle logminer cannot add duplicate logfileDBZ-3266

  • Oracle connector does not correctly handle partially committed transactionsDBZ-3322

  • Data loss when MongoDB snapshot take longer than the Oplog WindowDBZ-3331

  • First online log query does not limit results to those that are available.DBZ-3332

  • Connector crashing after running for some timeDBZ-3377

  • Broken links in downstream Monitoring chapterDBZ-3408

  • Broken links in User guide table of routing SMT configuration optionsDBZ-3410

  • Broken link to basic configuration example in downstream content-based routing topicDBZ-3412

  • Cassandra connector does not react on schema changes properlyDBZ-3417

  • Debezium mapped diagnostic contexts doesn’t workDBZ-3438

  • source.timestamp.mode=commit imposes a significant performance penaltyDBZ-3452

  • Timezone difference not considered inLagFromSourceInMillisecondscalculationDBZ-3456

  • "Found null value for non-optional schema" error when issuing TRUNCATE from Postgres on a table with a PKDBZ-3469

  • Connector crashes when table name contains '-' characterDBZ-3485

  • Kafka Clients in Debezium Server is not aligned with Debezium Kafka versionDBZ-3498

  • ReadToInsertEvent SMT needs to set ConfigDefDBZ-3508

  • Debezium configuration can be modified after instantiationDBZ-3514

  • Oracle redo log switch not detected when using multiple archiver process threadsDBZ-3516

  • Cannot enable binlog streaming when INITIAL_ONLY snapshot mode configuredDBZ-3529

  • Missing schema function in DDL ParserDBZ-3543

  • Retry logic for "No more data to read from socket" is too strictDBZ-3472

Other changes

  • Document new source block and fix formatting issuesDBZ-1614

  • Re-connect after "too many connections"DBZ-2300

  • Modularize doc for MongoDB componentDBZ-2334

  • Rebase Postgres snapshot modes on exported snapshotsDBZ-2337

  • Enable continuous JFR recordingDBZ-3082

  • Remove deprecated Oracle connector option "database.tablename.case.insensitive"DBZ-3240

  • Improve Oracle redo logs query to avoid de-duplication stepDBZ-3256

  • Migrate Jenkins CI to OCP 4.0 in PSI clouddbz - 3396

  • Remove Antlr-based DML ParserDBZ-3400

  • Update Oracle driver versionDBZ-3460

  • Incremental snapshot follow-up tasksDBZ-3500

  • Unnecessary NPE due to autoboxingDBZ-3519

  • Upgrade actions/cache to v2 version for formatting checkDBZ-3520

  • Improve documentation for Oracle supplemental logging requirementsDBZ-3521

  • SignalsIT leave table artifacts that cause other tests to failDBZ-3533

  • Mark xstream dependency as providedDBZ-3539

  • Add test for Oracle table without PKDBZ-832

Release 1.6.0.Alpha1(May 6th, 2021)

See thecomplete list of issues.

Kafka compatibility

This release has been built against Kafka Connect 2.7.0 and has been tested with version 2.7.0 of the Kafka brokers. See theKafka documentationfor 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.

当你决定升级其中一个连接器to 1.6.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.6.0.Alpha1 plugin files, and restart the connector using the same configuration. Upon restart, the 1.6.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

Debezium now requires Java 11 as a build and a runtime environment (DBZ-2875). The only exception is Debezium Cassandra connector that still uses Java 8.

New Features

  • Sink adapter for Apache KafkaDBZ-3382

  • Optimisation on MongoDB and MySQL connector for skipped.operationsDBZ-3403

  • Incremental snapshottingDBZ-3473

Fixes

  • io.debezium.text.ParsingException: no viable alternative at input 'IDNUMBER(4)GENERATEDBY'DBZ-1721

  • SKIPPED_OPERATIONS is added to CommonConnectorConfig.CONFIG_DEFINITION although it’s not implemented in all connectorsDBZ-2699

  • Snapshot fails when reading TIME, DATE, DATETIME fields in mysql from ResultSetDBZ-3238

  • Update to fabric8 kube client 5.xDBZ-3349

  • An exception in resolveOracleDatabaseVersion if system language is not EnglishDBZ-3397

  • Change strimzi branch in jenkins openshift-test job to mainDBZ-3404

  • Broken link in downstream Monitoring chapter 7.3DBZ-3409

  • Broken link in content-based routing chapter to page for downloading the SMT scripting archiveDBZ-3411

  • LogMinerDmlParser mishandles double single quotes in WHERE clausesDBZ-3413

  • Incorrectly formatted links in downstream automatic topic creation docDBZ-3414

  • SMT acronym incorrectly expanded in Debezium User GuideDBZ-3415

  • MariaDB — support privilege DDL in parserDBZ-3422

  • 改变oc适用于詹金斯openshift-test工作oc createDBZ-3423

  • SQL Server property (snapshot.select.statement.overrides) only matches 1st entry if comma-separated list also contains spacesDBZ-3429

  • Permission issue when running docker-compose or docker build as user not having uid 1001DBZ-3453

  • no viable alternative at input 'DROP TABLE IF EXISTS group' (Galera and MariaDB)DBZ-3467

  • Debezium MySQL connector does not process tables with partitionsDBZ-3468

  • The building tools' version in README doc is outdatedDBZ-3478

  • MySQL DATE default value parser rejects timestampDBZ-3497

  • MySQL8 GRANT statement not parsableDBZ-3499

Other changes

  • Config validation for Db2DBZ-3118

  • Add smoke test for UIDBZ-3133

  • Create new metric "CapturedTables"DBZ-3161

  • Handle deadlock issue for MySql build stuck for 6hDBZ-3233

  • Document using Connect REST API for log level changesDBZ-3270

  • User Guide corrections for SQL Server connectorDBZ-3297

  • User Guide corrections for Db2 connectorDBZ-3298

  • User Guide corrections for MySQL connectorDBZ-3299

  • User Guide corrections for MongoDB connectorDBZ-3300

  • Allow building the Oracle connector on CIDBZ-3365

  • Add tests for Protobuf ConverterDBZ-3369

  • Use current SQL Server container image for testing and examplesDBZ-3379

  • Reword prereq in downstream SQL Server connector docDBZ-3392

  • Duplicate entry in MySQL connector properties table formysql-property-skipped-operationsDBZ-3402

  • Docs clarification around tombstone eventsDBZ-3416

  • Validate logical server name contains only alpha-numerical charactersDBZ-3427

  • Provide a "quick" build profileDBZ-3449

  • Avoid warning about superfluous exclusion during packagingDBZ-3458

  • Upgrade binlog clientDBZ-3463

Baidu
map