Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Description to include Elastic 8.0 info #676

Open
wants to merge 3 commits into
base: 5.0.x
Choose a base branch
from
Open

Update Description to include Elastic 8.0 info #676

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9051578
Update Description to include Elastic 8.0 info
sp-gupta Feb 14, 2023
aa535ee
Update pom.xml
sp-gupta Mar 27, 2023
5fc7ecc
Update pom.xml
sp-gupta Mar 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 allows moving data from Kafka to Elasticsearch 2.x, 5.x, 6.x, and 7.x. It writes data from a topic in Kafka to an index in Elasticsearch and all data for a topic have the same type.
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 data for the topic have the same type.

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.

Expand Down