From f3d1cdca6fcbf0effed08df71d6354120531f324 Mon Sep 17 00:00:00 2001 From: ikbalkaya Date: Wed, 9 Nov 2022 08:55:14 +0000 Subject: [PATCH 1/3] Update source links --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 83e23a94..c089f619 100644 --- a/README.md +++ b/README.md @@ -244,7 +244,7 @@ transforms.RecordKeyCheck.message.name = #{key}_message `transforms.RecordKeyCheck.channel.name` must be exactly the same configuration as `channel` configuration in your connector. `transforms.RecordKeyCheck.message.name` is optional But when provided it must be set as exactly the same as `message.name` in your connector. -There is a separate [Dockerfile](https://github.com/ably/kafka-connect-ably/KeyCheckSMT/blob/prepare_connector_for_dlq_processing/Dockerfile) provided in this project which contains the custom SMT installation along with connector. If you want to build your own Docker image, you can copy the content of this to `Dockerfile` provided in this project. You can alternatively build your JAR from the [source code](https://github.com/ably/kafka-connect-ably/tree/prepare_connector_for_dlq_processing/KeyCheckSMT) and add it to your classpath. +There is a separate [Dockerfile](https://github.com/ably/kafka-connect-ably/blob/main/KeyCheckSMT/Dockerfile) provided in this project which contains the custom SMT installation along with connector. If you want to build your own Docker image, you can copy the content of this to `Dockerfile` provided in this project. You can alternatively build your JAR from the [source code](https://github.com/ably/kafka-connect-ably/blob/main/KeyCheckSMT) and add it to your classpath. Please use this SMT only if you use `#{key}` in your configuration values for channel name or message name. If you do not use `#{key}` in your configuration values, you must not use this SMT. Setting up dead letter queue for failed messages is out of scope of this document. We recommend you read [this blog post](https://www.confluent.io/en-gb/blog/kafka-connect-deep-dive-error-handling-dead-letter-queues/) to learn how to set up dead letter queue for failed messages. From 2d216e75e020d9209e114acb18e49ad624a25c73 Mon Sep 17 00:00:00 2001 From: ikbalkaya Date: Wed, 9 Nov 2022 09:23:05 +0000 Subject: [PATCH 2/3] Bump minor version --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index c80e3b45..adc8942c 100644 --- a/pom.xml +++ b/pom.xml @@ -5,7 +5,7 @@ com.ably.kafka.connect kafka-connect-ably - 2.0.3 + 2.1.0 jar From f73f9097543ef05edb2d774a058f47ee0b752603 Mon Sep 17 00:00:00 2001 From: ikbalkaya Date: Wed, 9 Nov 2022 09:46:07 +0000 Subject: [PATCH 3/3] Update changelog --- CHANGELOG.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b325c2a8..9aa91aa3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,14 @@ # Changelog -# Changelog +## [v2.1.0](https://github.com/ably/kafka-connect-ably/tree/v2.1.0) + +[Full Changelog](https://github.com/ably/kafka-connect-ably/compare/v2.0.3...v2.1.0) + +**Implemented enhancements:** + +- Provide ability for users to channel failed messages into a dead letter queue [\#90](https://github.com/ably/kafka-connect-ably/issues/90) +- Provide ability to skip a record when a key is absent and channel is configured with a key [\#85](https://github.com/ably/kafka-connect-ably/issues/85) +- Update docker-compose to include latest version of images [\#81](https://github.com/ably/kafka-connect-ably/issues/81) ## [v2.0.3](https://github.com/ably/kafka-connect-ably/tree/v2.0.3)