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

Jump to bottom

Fixed idempotency images names #851

Merged
merged 1 commit into from Jan 12, 2021
Merged

Fixed idempotency images names #851

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/modules/ROOT/pages/idempotency.adoc
View file
Open in desktop
Expand Up @@ -16,13 +16,13 @@ Suppose you're using a source connector of any kind. By using the idempotency fe

This means, in the Kafkish language, you won't ingest the same payload multiple times in the target Kafka topic.

image::ckc-idempontency-source.png[image]
image::ckc-idempotency-source.png[image]

In the sink scenario, we'll stream out of a Kafka topic multiple records, transform/convert/manipulate them and send them to an external system, like a messaging broker, a storage infra, a database etc.

In the Kafka topic used as source we may have multiple repeated records with the same payload or same metadata. Based on this information we can choose to skip the same records while sending data to the external system and for doing this we can leverage the idempotency feature of ckc.

image::ckc-idempontency-sink.png[image]
image::ckc-idempotency-sink.png[image]

== Camel-Kafka-connector idempotency configuration

Expand Down