This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/master by this push:
new 950a78b Added blog post for Camel-Kafka-connector 0.5.0 (#478)
950a78b is described below
commit 950a78b08acb083abb89b5cc3a1adb3a48de54ff
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Fri Sep 11 18:12:34 2020 +0200
Added blog post for Camel-Kafka-connector 0.5.0 (#478)
---
.../featured.png | Bin 0 -> 3975989 bytes
.../09/Camel-kafka-connector-050-Whatsnew/index.md | 60 +++++++++++++++++++++
2 files changed, 60 insertions(+)
diff --git
a/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/featured.png
b/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/featured.png
new file mode 100644
index 0000000..e5077f5
Binary files /dev/null and
b/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/featured.png differ
diff --git a/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/index.md
b/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/index.md
new file mode 100644
index 0000000..6285ffc
--- /dev/null
+++ b/content/blog/2020/09/Camel-kafka-connector-050-Whatsnew/index.md
@@ -0,0 +1,60 @@
+---
+title: "Apache Camel Kafka Connector 0.5.0: What's New"
+date: 2020-09-14
+authors: [oscerd, valdar]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel Kafka Connector 0.5.0
release.
+---
+
+Apache Camel Kafka Connector 0.5.0 has just been released.
+
+This is based on the non-LTS release of Apache Camel 3.5.0, this means we will
not provide patch releases, but use the release _as-is_.
+
+
+## So what's in this release?
+
+This release introduce bug fixes, improvements and new connectors obviously
+
+### New connectors
+
+The new connectors introduced in this release are the following:
+
+- ArangoDB: Perform operations on ArangoDb when used as a Document Database,
or as a Graph Database.
+- AWS2-STS: Manage AWS STS cluster instances using AWS SDK version 2.x.
+- Azure Eventhubs: The azure-eventhubs component which integrates Azure Event
Hubs using AMQP protocol.
+- JSonata: JSON to JSON transformation using JSONATA.
+- Minio: Store and retrieve objects from Minio Storage Service using Minio SDK.
+- OAI-PMH: Harvest metadata using OAI-PMH protocol.
+- Vert.x HTTP Client: Camel HTTP client support with Vert.x.
+- Vert.x WebSocket: Camel WebSocket support with Vert.x.
+
+### Support for multiple topics from the source side
+
+Users are now able to specify multiple topics as target for the source
connector configuration.
+This field needs a comma-separated list of topics.
+
+### Documentation
+
+The documentation of each connector (source/sink or both) now contains
reference to the following information
+
+- Explicit connector class to be used
+- Converters list available in the connector as out of the box solutions
+- Transformers list available in the connector as out of the box solutions
+- Aggregation Strategies list available in the connector as out of the box
solutions
+
+On the Archetypes side: the archetype provided to extend the current
connectors is now able to use a parameter to specify what connector you want to
extend.
+More information available at [Camel-Kafka-connector archetype
documentation](https://camel.apache.org/camel-kafka-connector/latest/archetypes.html).
+
+We added also a troubleshooting section in our documentation, to be able to
debug and use the connectors in the best way possible.
+
+### Improved performance
+
+Thanks to our users we found out we could improve the performance of Source
connectors: more details at
https://github.com/apache/camel-kafka-connector/issues/414
+
+### Examples
+
+We added a bunch of new examples to the [camel-kafka-connector-examples
repository](https://github.com/apache/camel-kafka-connector-examples)
+
+### What to expect
+
+We are already working on the next release based on the upcoming 3.6.0 Camel
release: we'll add new connectors, we'll improve the user experience and we'll
focus on improving the codebase and introducing new features.
