What's New

What's New in 1.13

• Added a custom authentication provider interface for Source and Sink Connectors. This feature enables you to write and use a custom implementation class in your connector. To learn more, see the Custom Authentication Provider guide.

• Fixed an issue that occurred when validating configuration for Source and Sink Connectors if the configuration contained secrets and used the Provider framework. To learn more about this fix, see the KAFKA-414 JIRA issue.

What's New in 1.12

• Added support for a data configuration value in the mongo.errors.tolerance configuration setting. With mongo.errors.tolerance=data, the sink connector tolerates only data errors, and fails for any others.

What's New in 1.11.2

• Fixed a bug in which unsuccessful attempts to retrieve items from a change stream were logged at the INFO level instead of at ERROR level. To learn more about this fix, see the KAFKA-396 JIRA issue.

• Fixed a bug in which requirements for the DELETE_WRITEMODEL_STRATEGY_CONFIG String value prevented the creation of a DeleteOneDefaultStrategy object. To learn more about this fix, see the KAFKA-395 JIRA issue.

What's New in 1.11.1

• Fixed wildcard matching on partial field names in documents. To learn more about this fix, see the KAFKA-391 JIRA issue.

• Fixed an issue in which a null pointer exception is thrown when the connector attempts to log null values on configuration settings. To learn more about this fix, see the KAFKA-390 JIRA issue.

What's New in 1.11

• Added support for regular expressions in the topic.namespace.map property. To learn more about this feature and see an example of its use, see the Regular Expressions usage example in the Topic Naming page.

• Added support for setting a custom delete write model strategy by using the delete.writemodel.strategy configuration property. To learn more, see Sink Connector Write Model Strategies.

• Added the UpdateOneDefaultStrategy write model strategy. To learn more, see the list of Write Model Strategies.

• Added the change.stream.document.key.as.key source connector configuration property. When set to true, the connector adds keys of the deleted documents to the tombstone events. When set to false, the connector uses the resume token as the source key for the tombstone events.

  Because this property is set to true by default, this might be a breaking change for some users. To learn more, see the list of Change Stream Properties.

• DDL events from Debezium are recorded as no-ops and no longer cause an error.

What's New in 1.10.1

• Fixed a resource leak related to MongoSourceTask.start that was introduced in version 1.9.

What's New in 1.10

• Added the connector name to JMX monitoring metrics.

• Added support for SSL by creating the following configuration options:

  • connection.ssl.truststore

  • connection.ssl.truststorePassword

  • connection.ssl.keystore

  • connection.ssl.keystorePassword

• Ensured the driver parses config values from config providers before validating them.

What's New in 1.9.1

• Corrected the behavior of schema inference for documents in nested arrays.

What's New in 1.9

• Introduced the startup.mode=timestamp setting that allows you to start a Change Stream at a specific timestamp by setting the new startup.mode.timestamp.start.at.operation.time property.

• Deprecated the copy.existing property and all copy.existing.* properties. Use the startup.mode=copy_existing and the startup.mode.copy.existing.* properties to configure the copy existing feature.

• Introduced the change.stream.full.document.before.change setting that allows you to access and configure the pre-image of an update operation in the change stream event document.

• Improved schema inference for nested documents contained in arrays.

• Introduced the publish.full.document.only.tombstones.on.delete setting that configures the connector to send tombstone events when documents are deleted. This setting only applies when publish.full.document.only is true.

• Added MongoDB server exception information to dead letter queue messages.

What's New in 1.8.1

• Corrected the type returned by getAttribute() and getAttributes() method calls in JMX MBeans to Attribute.

What's New in 1.8

• Updated the MongoDB Java driver dependency to version 4.7.

• Added several logger events and details in source and sink connectors to help with debugging. For a complete list of updates, see the KAFKA-302 issue in JIRA.

• Added JMX monitoring support for the source and sink connectors. To learn more about monitoring connectors, see the Monitoring page.

What's New in 1.7

• Updated the MongoDB Java driver dependency to version 4.5

connection.uri=mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myRepl&retryWrites=false

What's New in 1.6.1

• Updated MongoDB Java driver dependency to 4.3.1 in the combined JARs

What's New in 1.6

• Added support for Stable API to force the server to run operations with behavior compatible with the specified API version

  Note

  Starting from February 2022, the Versioned API is known the Stable API. All concepts and features remain the same with this naming change.

• Added error handling properties for the sink connector and source connector that can override the Kafka Connect framework's error handling behavior

• Added mongo-kafka-connect-<version>-confluent.jar, which contains the connector and all dependencies required to run it on the Confluent Platform

What's New in 1.5

• Updated the MongoDB Java driver dependency to version 4.2

What's New in 1.4

• Updated the MongoDB Java Driver to version 4.1

What's New in 1.3

• Added automated integration testing for the latest Kafka Connector and Confluent Platform versions to ensure compatibility

What's New in 1.2

What's New in 1.1

What's New in 1.0

The initial GA release.