Update pom.xml

confluentinc · Mar 27, 2023 · 5fc7ecc · 5fc7ecc
1 parent aa535ee
commit 5fc7ecc
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/pom.xml b/pom.xml
@@ -150,7 +150,7 @@
                             <title>Kafka Connect Elasticsearch</title>
                             <documentationUrl>https://docs.confluent.io/${project.version}/connect/connect-elasticsearch/docs/index.html</documentationUrl>
                             <description>
-                                The Elasticsearch connector moves data from Kafka to Elasticsearch 2.x, 5.x, 6.x, 7.x, and 8.x. Elasticsearch version support depends the connector version. Newer connector versions may not support older versions of Elasticsearch. Elasticsearch 8.x support was introduced with connector version 14.0.0. This connector version writes data from a topic in Kafka to an index in Elasticsearch and all datatypes from the topic remain consistent when the data moves to Elasticsearch.
+                                The Elasticsearch connector moves data from Kafka to Elasticsearch 2.x, 5.x, 6.x, 7.x, and 8.x. Elasticsearch version support depends the connector version. Newer connector versions may not support older versions of Elasticsearch. Elasticsearch 8.x support was introduced with connector version 14.0.0. This connector version writes data from a topic in Kafka to an index in Elasticsearch and all datatypes from the data inside topic remain consistent when it moves to Elasticsearch.
 
                                 Elasticsearch is often used for text queries, analytics and as an key-value store (use cases). The connector covers both the analytics and key-value store use cases. For the analytics use case, each message is in Kafka is treated as an event and the connector uses topic+partition+offset as a unique identifier for events, which then converted to unique documents in Elasticsearch. For the key-value store use case, it supports using keys from Kafka messages as document ids in Elasticsearch and provides configurations ensuring that updates to a key are written to Elasticsearch in order. For both use cases, Elasticsearch’s idempotent write semantics guarantees exactly once delivery.