This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-3.18.x
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 7e70876686dc42314f601141ba2b3e207485fd72
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Aug 8 13:10:37 2022 +0200
camel-debezium - Update links in docs to latest release.
---
.../camel-debezium-db2/src/main/docs/debezium-db2-component.adoc | 6 ++----
.../src/main/docs/debezium-mongodb-component.adoc | 8 +++-----
.../src/main/docs/debezium-mysql-component.adoc | 8 +++-----
.../src/main/docs/debezium-oracle-component.adoc | 8 +++-----
.../src/main/docs/debezium-postgres-component.adoc | 8 +++-----
.../src/main/docs/debezium-sqlserver-component.adoc | 8 +++-----
6 files changed, 17 insertions(+), 29 deletions(-)
diff --git
a/components/camel-debezium/camel-debezium-db2/src/main/docs/debezium-db2-component.adoc
b/components/camel-debezium/camel-debezium-db2/src/main/docs/debezium-db2-component.adoc
index 92fe5c99764..cdafcbeffe5 100644
---
a/components/camel-debezium/camel-debezium-db2/src/main/docs/debezium-db2-component.adoc
+++
b/components/camel-debezium/camel-debezium-db2/src/main/docs/debezium-db2-component.adoc
@@ -15,14 +15,12 @@
*{component-header}*
-The Debezium db2 component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/1.8/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from db2 database using Debezium
without the need for Kafka or Kafka Connect.
+The Debezium db2 component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/1.8/operations/embedded.html[Debezium
Engine], which enables Change Data Capture from db2 database using Debezium
without the need for Kafka or Kafka Connect.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium db2 component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
diff --git
a/components/camel-debezium/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
b/components/camel-debezium/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
index b93b29c7503..5305b9277c4 100644
---
a/components/camel-debezium/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
+++
b/components/camel-debezium/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
@@ -14,17 +14,15 @@
*{component-header}*
-The Debezium MongoDB component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/0.9/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from MongoDB database using
Debezium without the need for Kafka or Kafka Connect.
+The Debezium MongoDB component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/1.9/development/engine.html[Debezium
Engine], which enables Change Data Capture from MongoDB database using
Debezium without the need for Kafka or Kafka Connect.
*Note:* The Debezium MongoDB connector uses MongoDB’s oplog to capture the
changes, so the connector works only with MongoDB replica sets or with sharded
clusters where each shard is a separate replica set, therefore you will need to
have your MongoDB instance running either in replica set mode
or sharded clusters mode.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium Mongodb component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
@@ -96,7 +94,7 @@
from("debezium-mongodb:dbz-test-1?offsetStorageFileName=/usr/offset-file-1.dat&m
By default, the component will emit the events in the body String JSON format
in case of `u`, `c` or `r` operations, this can be easily converted to JSON
using Camel JSON Data Format e.g: `.unmarshal().json()` like the above example.
In case of operation `d`, the body will be `null`.
-*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
failures].
+*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/1.9/development/engine.html#_handling_failures[handling
failures].
include::spring-boot:partial$starter.adoc[]
diff --git
a/components/camel-debezium/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
b/components/camel-debezium/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
index 03ba539c674..170cab645a0 100644
---
a/components/camel-debezium/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
+++
b/components/camel-debezium/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
@@ -14,14 +14,12 @@
*{component-header}*
-The Debezium MySQL component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/0.9/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from MySQL database using
Debezium without the need for Kafka or Kafka Connect.
+The Debezium MySQL component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/1.9/development/engine.html[Debezium
Engine], which enables Change Data Capture from MySQL database using Debezium
without the need for Kafka or Kafka Connect.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium MySQL component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
@@ -116,7 +114,7 @@ from("debezium-mysql:[name]?[options]])
});
----
-*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
failures].
+*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/1.9/development/engine.html#_handling_failures[handling
failures].
include::spring-boot:partial$starter.adoc[]
diff --git
a/components/camel-debezium/camel-debezium-oracle/src/main/docs/debezium-oracle-component.adoc
b/components/camel-debezium/camel-debezium-oracle/src/main/docs/debezium-oracle-component.adoc
index 72b7c85af2d..c35e3eef3ef 100644
---
a/components/camel-debezium/camel-debezium-oracle/src/main/docs/debezium-oracle-component.adoc
+++
b/components/camel-debezium/camel-debezium-oracle/src/main/docs/debezium-oracle-component.adoc
@@ -15,14 +15,12 @@
*{component-header}*
-The Debezium oracle component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/0.9/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from oracle database using
Debezium without the need for Kafka or Kafka Connect.
+The Debezium oracle component is wrapper around https://debezium.io/[Debezium]
using
https://debezium.io/documentation/reference/1.9/development/engine.html[Debezium
Engine], which enables Change Data Capture from oracle database using Debezium
without the need for Kafka or Kafka Connect.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium oracle component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
@@ -107,7 +105,7 @@ from("debezium-oracle:[name]?[options]])
});
----
-*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
failures].
+*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/1.9/development/engine.html#_handling_failures[handling
failures].
include::spring-boot:partial$starter.adoc[]
diff --git
a/components/camel-debezium/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
b/components/camel-debezium/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
index 7c529af8c21..fa372751669 100644
---
a/components/camel-debezium/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
+++
b/components/camel-debezium/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
@@ -15,14 +15,12 @@
*{component-header}*
-The Debezium PostgresSQL component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/0.9/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from PostgresSQL database using
Debezium without the need for Kafka or Kafka Connect.
+The Debezium PostgresSQL component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/1.9/development/engine.html[Debezium
Engine], which enables Change Data Capture from PostgresSQL database using
Debezium without the need for Kafka or Kafka Connect.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium PostgresSQL component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
@@ -107,7 +105,7 @@ from("debezium-postgres:[name]?[options]])
});
----
-*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
failures].
+*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/1.9/development/engine.html#_handling_failures[handling
failures].
include::spring-boot:partial$starter.adoc[]
diff --git
a/components/camel-debezium/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
b/components/camel-debezium/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
index 4fa363b8cc4..90134bedfd3 100644
---
a/components/camel-debezium/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
+++
b/components/camel-debezium/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
@@ -14,14 +14,12 @@
*{component-header}*
-The Debezium SQL Server component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/0.10/operations/embedded.html[Debezium
Embedded], which enables Change Data Capture from SQL Server database using
Debezium without the need for Kafka or Kafka Connect.
+The Debezium SQL Server component is wrapper around
https://debezium.io/[Debezium] using
https://debezium.io/documentation/reference/0.10/operations/embedded.html[Debezium
Engine], which enables Change Data Capture from SQL Server database using
Debezium without the need for Kafka or Kafka Connect.
-*Note on handling failures:* Per
https://debezium.io/documentation/reference/0.10/operations/embedded.html#_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.
+*Note on handling failures:* Per
https://debezium.io/documentation/reference/1.9/development/engine.html#_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 in receiving duplicate events immediately after the restart.
Therefore, your downstream routes should be tolerant enough of such case and
deduplicate events if needed.
-*Note:* The Debezium SQL Server component is currently not supported in OSGi
-
Maven users will need to add the following dependency to their `pom.xml`
for this component.
@@ -105,7 +103,7 @@ from("debezium-sqlserver:[name]?[options]])
});
----
-*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
failures].
+*Important Note:* This component is a thin wrapper around Debezium Engine as
mentioned, therefore before using this component in production, you need to
understand how Debezium works and how configurations can reflect the expected
behavior, especially in regards to
https://debezium.io/documentation/reference/1.9/development/engine.html#_handling_failures[handling
failures].
include::spring-boot:partial$starter.adoc[]
