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.git
commit 075d9398ef6b0fdeafebe8f2226af87d220b605b
Author: Omar Al-Safi <omars...@gmail.com>
AuthorDate: Fri Sep 6 16:23:22 2019 +0200
Update components/camel-debezium/src/main/docs/debezium-component.adoc
Co-Authored-By: Gunnar Morling <gunnar.morl...@googlemail.com>
---
components/camel-debezium/src/main/docs/debezium-component.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/components/camel-debezium/src/main/docs/debezium-component.adoc
b/components/camel-debezium/src/main/docs/debezium-component.adoc
index 74122a2..8cd3526 100644
--- a/components/camel-debezium/src/main/docs/debezium-component.adoc
+++ b/components/camel-debezium/src/main/docs/debezium-component.adoc
@@ -7,7 +7,7 @@ The Debezium component is wrapper around
https://debezium.io/[Debezium] using ht
*Note on handling failures:* Per
https://debezium.io/docs/embedded/#handling_failures[Debezium Embedded Engine]
documentation, the engines is actively recording source offsets and
periodically flushes these offsets to a persistent storage, so when the
application is restarted or crashed, the engine will resume from the last
recorded offset.
Thus, at normal operation, your downstream routes will receive each event
exactly once, however in case of an application crash (not having a graceful
shutdown), the application will resume from the last recorded offset,
-which may result of receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
+which may result in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
Maven users will need to add the following dependency to their `pom.xml`
for this component.
