You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/10/31 13:00:46 UTC
[camel] branch master updated: CAMEL-14116: Ignore non-ascii chars
from description and move javaDocs into the setters instead of fields
(#3303)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 354c301 CAMEL-14116: Ignore non-ascii chars from description and move javaDocs into the setters instead of fields (#3303)
354c301 is described below
commit 354c301f04b96fcdad85fae80e48419f1c4a7438
Author: Omar Al-Safi <om...@gmail.com>
AuthorDate: Thu Oct 31 14:00:21 2019 +0100
CAMEL-14116: Ignore non-ascii chars from description and move javaDocs into the setters instead of fields (#3303)
Signed-off-by: Omar Al-Safi <om...@gmail.com>
---
.../EmbeddedDebeziumConfiguration.java | 4 +-
.../camel/maven/config/ConnectorConfigField.java | 9 +-
.../maven/config/ConnectorConfigGenerator.java | 18 +-
.../src/main/docs/debezium-mysql-component.adoc | 118 ++--
.../src/main/docs/debezium-postgres-component.adoc | 92 ++--
.../DebeziumMySqlComponentConfiguration.java | 608 ++++++++-------------
.../DebeziumPostgresComponentConfiguration.java | 283 +++++-----
7 files changed, 498 insertions(+), 634 deletions(-)
diff --git a/components/camel-debezium-common/camel-debezium-common-component/src/main/java/org/apache/camel/component/debezium/configuration/EmbeddedDebeziumConfiguration.java b/components/camel-debezium-common/camel-debezium-common-component/src/main/java/org/apache/camel/component/debezium/configuration/EmbeddedDebeziumConfiguration.java
index 193d8d8..f9fa0bd 100644
--- a/components/camel-debezium-common/camel-debezium-common-component/src/main/java/org/apache/camel/component/debezium/configuration/EmbeddedDebeziumConfiguration.java
+++ b/components/camel-debezium-common/camel-debezium-common-component/src/main/java/org/apache/camel/component/debezium/configuration/EmbeddedDebeziumConfiguration.java
@@ -270,7 +270,7 @@ public abstract class EmbeddedDebeziumConfiguration {
* The name of the Java class of the commit policy. It defines when offsets
* commit has to be triggered based on the number of events processed and the
* time elapsed since the last commit. This class must implement the interface
- * <…>.OffsetCommitPolicy. The default is a periodic commit policy based upon
+ * 'OffsetCommitPolicy'. The default is a periodic commit policy based upon
* time intervals.
*/
public String getOffsetCommitPolicy() {
@@ -308,7 +308,7 @@ public abstract class EmbeddedDebeziumConfiguration {
/**
* The number of partitions used when creating the offset storage topic.
- * Required when offset.storage is set to the <…>.KafkaOffsetBackingStore.
+ * Required when offset.storage is set to the 'KafkaOffsetBackingStore'.
*/
public int getOffsetStoragePartitions() {
return offsetStoragePartitions;
diff --git a/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigField.java b/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigField.java
index ce89442..2efa345 100644
--- a/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigField.java
+++ b/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigField.java
@@ -84,7 +84,10 @@ public class ConnectorConfigField {
}
public String getDescription() {
- return fieldDef.documentation;
+ if (fieldDef.documentation != null) {
+ return removeNonAsciiChars(fieldDef.documentation);
+ }
+ return "";
}
private String getSetterMethodName(final String name) {
@@ -124,4 +127,8 @@ public class ConnectorConfigField {
}
return null;
}
+
+ private String removeNonAsciiChars(final String text) {
+ return text.replaceAll("[^\\x00-\\x7F]", "");
+ }
}
diff --git a/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigGenerator.java b/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigGenerator.java
index 0d3f8cf..4893914 100644
--- a/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigGenerator.java
+++ b/components/camel-debezium-common/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/config/ConnectorConfigGenerator.java
@@ -183,14 +183,6 @@ public final class ConnectorConfigGenerator {
field.setLiteralInitializer(fieldConfig.getDefaultValueAsString());
}
- String description = fieldConfig.getDescription();
-
- if (description == null || description.isEmpty()) {
- description = String.format("Description is not available here, please check Debezium website for corresponding key '%s' description.", fieldName);
- }
-
- field.getJavaDoc().setText(description);
-
final Annotation annotation = field.addAnnotation(UriParam.class)
.setLiteralValue("label", "LABEL_NAME");
@@ -211,13 +203,21 @@ public final class ConnectorConfigGenerator {
dbzConfigFields.forEach((fieldName, fieldConfig) -> {
if (!isFieldInternalOrDeprecated(fieldConfig)) {
// setters with javaDoc
- javaClass.addMethod()
+ final Method method = javaClass.addMethod()
.setName(fieldConfig.getFieldSetterMethodName())
.addParameter(fieldConfig.getRawType(), fieldConfig.getFieldName())
.setPublic()
.setReturnType(Void.TYPE)
.setBody(String.format("this.%1$s = %1$s;", fieldConfig.getFieldName()));
+ String description = fieldConfig.getDescription();
+
+ if (description == null || description.isEmpty()) {
+ description = String.format("Description is not available here, please check Debezium website for corresponding key '%s' description.", fieldName);
+ }
+
+ method.getJavaDoc().setFullText(description);
+
// getters
javaClass.addMethod()
.setName(fieldConfig.getFieldGetterMethodName())
diff --git a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
index 0181e47..2dbbabd 100644
--- a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
+++ b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
@@ -87,12 +87,12 @@ with the following path and query parameters:
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
| *internalKeyConverter* (consumer) | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
| *internalValueConverter* (consumer) | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface .OffsetCommitPolicy. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
| *offsetCommitTimeoutMs* (consumer) | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000 | long
| *offsetFlushIntervalMs* (consumer) | Interval at which to try committing offsets. The default is 1 minute. | 60000 | long
| *offsetStorage* (consumer) | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
| *offsetStorageFileName* (consumer) | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore | | String
-| *offsetStoragePartitions* (consumer) | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the .KafkaOffsetBackingStore. | | int
+| *offsetStoragePartitions* (consumer) | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | int
| *offsetStorageReplication Factor* (consumer) | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | int
| *offsetStorageTopic* (consumer) | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
@@ -181,74 +181,74 @@ The component supports 70 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-mysql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
-| *camel.component.debezium-mysql.configuration.bigint-unsigned-handling-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. F [...]
-| *camel.component.debezium-mysql.configuration.binlog-buffer-size* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
-| *camel.component.debezium-mysql.configuration.column-blacklist* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reaso [...]
-| *camel.component.debezium-mysql.configuration.connect-keep-alive* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
-| *camel.component.debezium-mysql.configuration.connect-keep-alive-interval-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. [...]
-| *camel.component.debezium-mysql.configuration.connect-timeout-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
+| *camel.component.debezium-mysql.configuration.bigint-unsigned-handling-mode* | Specify how BIGINT UNSIGNED columns should be represented in change events, including:'precise' uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents values using Java's 'long', which may not offer the precision but will be far easier to use in consum [...]
+| *camel.component.debezium-mysql.configuration.binlog-buffer-size* | The size of a look-ahead buffer used by the binlog reader to decide whether the transaction in progress is going to be committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 (i.e. buffering is disabled). | 0 | Integer
+| *camel.component.debezium-mysql.configuration.column-blacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | | String
+| *camel.component.debezium-mysql.configuration.connect-keep-alive* | Whether a separate thread should be used to ensure the connection is kept alive. | true | Boolean
+| *camel.component.debezium-mysql.configuration.connect-keep-alive-interval-ms* | Interval in milliseconds to wait for connection checking if keep alive thread is used. | 60000 | Long
+| *camel.component.debezium-mysql.configuration.connect-timeout-ms* | Maximum time in milliseconds to wait after trying to connect to the database before timing out. | 30000 | Integer
| *camel.component.debezium-mysql.configuration.connector-class* | The name of the Java class for the connector | | Class
-| *camel.component.debezium-mysql.configuration.database-blacklist* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
-| *camel.component.debezium-mysql.configuration.database-history* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reaso [...]
-| *camel.component.debezium-mysql.configuration.database-history-file-filename* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. [...]
-| *camel.component.debezium-mysql.configuration.database-history-kafka-bootstrap-servers* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the chan [...]
-| *camel.component.debezium-mysql.configuration.database-history-kafka-recovery-attempts* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the chan [...]
-| *camel.component.debezium-mysql.configuration.database-history-kafka-recovery-poll-interval-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in [...]
-| *camel.component.debezium-mysql.configuration.database-history-kafka-topic* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. Fo [...]
-| *camel.component.debezium-mysql.configuration.database-history-skip-unparseable-ddl* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change [...]
-| *camel.component.debezium-mysql.configuration.database-history-store-only-monitored-tables-ddl* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in [...]
-| *camel.component.debezium-mysql.configuration.database-hostname* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reas [...]
-| *camel.component.debezium-mysql.configuration.database-initial-statements* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For [...]
-| *camel.component.debezium-mysql.configuration.database-jdbc-driver* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.database-password* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reas [...]
-| *camel.component.debezium-mysql.configuration.database-port* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason t [...]
-| *camel.component.debezium-mysql.configuration.database-server-id* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
-| *camel.component.debezium-mysql.configuration.database-server-id-offset* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For t [...]
-| *camel.component.debezium-mysql.configuration.database-server-name* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.database-ssl-keystore* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this [...]
-| *camel.component.debezium-mysql.configuration.database-ssl-keystore-password* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. [...]
-| *camel.component.debezium-mysql.configuration.database-ssl-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reas [...]
-| *camel.component.debezium-mysql.configuration.database-ssl-truststore* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For thi [...]
-| *camel.component.debezium-mysql.configuration.database-ssl-truststore-password* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event [...]
-| *camel.component.debezium-mysql.configuration.database-user* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason t [...]
-| *camel.component.debezium-mysql.configuration.database-whitelist* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this rea [...]
-| *camel.component.debezium-mysql.configuration.ddl-parser-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason [...]
-| *camel.component.debezium-mysql.configuration.decimal-handling-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this [...]
-| *camel.component.debezium-mysql.configuration.enable-time-adjuster* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.event-deserialization-failure-handling-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the c [...]
-| *camel.component.debezium-mysql.configuration.gtid-new-channel-position* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For t [...]
-| *camel.component.debezium-mysql.configuration.gtid-source-excludes* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.gtid-source-filter-dml-events* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. F [...]
-| *camel.component.debezium-mysql.configuration.gtid-source-includes* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.heartbeat-interval-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this [...]
-| *camel.component.debezium-mysql.configuration.heartbeat-topics-prefix* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For thi [...]
+| *camel.component.debezium-mysql.configuration.database-blacklist* | Description is not available here, please check Debezium website for corresponding key 'database.blacklist' description. | | String
+| *camel.component.debezium-mysql.configuration.database-history* | The name of the DatabaseHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'database.history.' string. | io.debezium.relational.history.FileDatabaseHistory | String
+| *camel.component.debezium-mysql.configuration.database-history-file-filename* | The path to the file that will be used to record the database history | | String
+| *camel.component.debezium-mysql.configuration.database-history-kafka-bootstrap-servers* | A list of host/port pairs that the connector will use for establishing the initial connection to the Kafka cluster for retrieving database schema history previously stored by the connector. This should point to the same Kafka cluster used by the Kafka Connect process. | | String
+| *camel.component.debezium-mysql.configuration.database-history-kafka-recovery-attempts* | The number of attempts in a row that no data are returned from Kafka before recover completes. The maximum amount of time to wait after receiving no data is (recovery.attempts) x (recovery.poll.interval.ms). | 100 | Integer
+| *camel.component.debezium-mysql.configuration.database-history-kafka-recovery-poll-interval-ms* | The number of milliseconds to wait while polling for persisted data during recovery. | 100 | Integer
+| *camel.component.debezium-mysql.configuration.database-history-kafka-topic* | The name of the topic for the database schema history | | String
+| *camel.component.debezium-mysql.configuration.database-history-skip-unparseable-ddl* | Controls the action Debezium will take when it meets a DDL statement in binlog, that it cannot parse.By default the connector will stop operating but by changing the setting it can ignore the statements which it cannot parse. If skipping is enabled then Debezium can miss metadata changes. | false | Boolean
+| *camel.component.debezium-mysql.configuration.database-history-store-only-monitored-tables-ddl* | Controls what DDL will Debezium store in database history.By default (false) Debezium will store all incoming DDL statements. If set to truethen only DDL that manipulates a monitored table will be stored. | false | Boolean
+| *camel.component.debezium-mysql.configuration.database-hostname* | Resolvable hostname or IP address of the MySQL database server. | | String
+| *camel.component.debezium-mysql.configuration.database-initial-statements* | A semicolon separated list of SQL statements to be executed when a JDBC connection (not binlog reading connection) to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configuration of session parameters only,but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not a [...]
+| *camel.component.debezium-mysql.configuration.database-jdbc-driver* | JDBC Driver class name used to connect to the MySQL database server. | class com.mysql.cj.jdbc.Driver | String
+| *camel.component.debezium-mysql.configuration.database-password* | Password of the MySQL database user to be used when connecting to the database. | | String
+| *camel.component.debezium-mysql.configuration.database-port* | Port of the MySQL database server. | 3306 | Integer
+| *camel.component.debezium-mysql.configuration.database-server-id* | A numeric ID of this database client, which must be unique across all currently-running database processes in the cluster. This connector joins the MySQL database cluster as another server (with this unique ID) so it can read the binlog. By default, a random number is generated between 5400 and 6400. | | Long
+| *camel.component.debezium-mysql.configuration.database-server-id-offset* | Only relevant if parallel snapshotting is configured. During parallel snapshotting, multiple (4) connections open to the database client, and they each need their own unique connection ID. This offset is used to generate those IDs from the base configured cluster ID. | 10000 | Long
+| *camel.component.debezium-mysql.configuration.database-server-name* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | | String
+| *camel.component.debezium-mysql.configuration.database-ssl-keystore* | Location of the Java keystore file containing an application process's own certificate and private key. | | String
+| *camel.component.debezium-mysql.configuration.database-ssl-keystore-password* | Password to access the private key from the keystore file specified by 'ssl.keystore' configuration property or the 'javax.net.ssl.keyStore' system or JVM property. This password is used to unlock the keystore file (store password), and to decrypt the private key stored in the keystore (key password). | | String
+| *camel.component.debezium-mysql.configuration.database-ssl-mode* | Whether to use an encrypted connection to MySQL. Options include'disabled' (the default) to use an unencrypted connection; 'preferred' to establish a secure (encrypted) connection if the server supports secure connections, but fall back to an unencrypted connection otherwise; 'required' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify_ca' like 'required' but additionally verify the [...]
+| *camel.component.debezium-mysql.configuration.database-ssl-truststore* | Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). | | String
+| *camel.component.debezium-mysql.configuration.database-ssl-truststore-password* | Password to unlock the keystore file (store password) specified by 'ssl.trustore' configuration property or the 'javax.net.ssl.trustStore' system or JVM property. | | String
+| *camel.component.debezium-mysql.configuration.database-user* | Name of the MySQL database user to be used when connecting to the database. | | String
+| *camel.component.debezium-mysql.configuration.database-whitelist* | The databases for which changes are to be captured | | String
+| *camel.component.debezium-mysql.configuration.ddl-parser-mode* | MySQL DDL statements can be parsed in different ways:'legacy' parsing is creating a TokenStream and comparing token by token with an expected values.The decisions are made by matched token values.'antlr' (the default) uses generated parser from MySQL grammar using ANTLR v4 tool which use ALL(*) algorithm for parsing.This parser creates a parsing tree for DDL statement, then walks trough it and apply changes by node types [...]
+| *camel.component.debezium-mysql.configuration.decimal-handling-mode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precisi [...]
+| *camel.component.debezium-mysql.configuration.enable-time-adjuster* | MySQL allows user to insert year value as either 2-digit or 4-digit. In case of two digit the value is automatically mapped into 1970 - 2069.false - delegates the implicit conversion to the databasetrue - (the default) Debezium makes the conversion | true | Boolean
+| *camel.component.debezium-mysql.configuration.event-deserialization-failure-handling-mode* | Specify how failures during deserialization of binlog events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event will be skipped;'ignore' the problematic ev [...]
+| *camel.component.debezium-mysql.configuration.gtid-new-channel-position* | If set to 'latest', when connector sees new GTID, it will start consuming gtid channel from the server latest executed gtid position. If 'earliest' connector starts reading channel from first available (not purged) gtid position on the server. | latest | String
+| *camel.component.debezium-mysql.configuration.gtid-source-excludes* | The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog. | | String
+| *camel.component.debezium-mysql.configuration.gtid-source-filter-dml-events* | If set to true, we will only produce DML events into Kafka for transactions that were written on mysql servers with UUIDs matching the filters defined by the gtid.source.includes or gtid.source.excludes configuration options, if they are specified. | true | Boolean
+| *camel.component.debezium-mysql.configuration.gtid-source-includes* | The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog. | | String
+| *camel.component.debezium-mysql.configuration.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | Integer
+| *camel.component.debezium-mysql.configuration.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
| *camel.component.debezium-mysql.configuration.include-query* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason t [...]
-| *camel.component.debezium-mysql.configuration.include-schema-changes* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this [...]
-| *camel.component.debezium-mysql.configuration.inconsistent-schema-handling-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change even [...]
+| *camel.component.debezium-mysql.configuration.include-schema-changes* | Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value includes the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. | true | Boolean
+| *camel.component.debezium-mysql.configuration.inconsistent-schema-handling-mode* | Specify how binlog events that belong to a table missing from internal schema representation (i.e. internal representation is not consistent with database) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event w [...]
| *camel.component.debezium-mysql.configuration.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
| *camel.component.debezium-mysql.configuration.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-mysql.configuration.max-batch-size* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason [...]
-| *camel.component.debezium-mysql.configuration.max-queue-size* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason [...]
+| *camel.component.debezium-mysql.configuration.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
+| *camel.component.debezium-mysql.configuration.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
| *camel.component.debezium-mysql.configuration.name* | Unique name for the connector. Attempting to register again with the same name will fail. | | String
-| *camel.component.debezium-mysql.configuration.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface <…>.OffsetCommitPolicy. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *camel.component.debezium-mysql.configuration.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
| *camel.component.debezium-mysql.configuration.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000 | Long
| *camel.component.debezium-mysql.configuration.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. | 60000 | Long
| *camel.component.debezium-mysql.configuration.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
| *camel.component.debezium-mysql.configuration.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore | | String
-| *camel.component.debezium-mysql.configuration.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the <…>.KafkaOffsetBackingStore. | | Integer
+| *camel.component.debezium-mysql.configuration.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
| *camel.component.debezium-mysql.configuration.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
| *camel.component.debezium-mysql.configuration.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-mysql.configuration.poll-interval-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reaso [...]
-| *camel.component.debezium-mysql.configuration.snapshot-delay-ms* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reas [...]
-| *camel.component.debezium-mysql.configuration.snapshot-fetch-size* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this re [...]
-| *camel.component.debezium-mysql.configuration.snapshot-locking-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this [...]
-| *camel.component.debezium-mysql.configuration.snapshot-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason t [...]
-| *camel.component.debezium-mysql.configuration.snapshot-new-tables* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this re [...]
-| *camel.component.debezium-mysql.configuration.table-blacklist* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason [...]
-| *camel.component.debezium-mysql.configuration.table-ignore-builtin* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
-| *camel.component.debezium-mysql.configuration.table-whitelist* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason [...]
-| *camel.component.debezium-mysql.configuration.time-precision-mode* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this re [...]
-| *camel.component.debezium-mysql.configuration.tombstones-on-delete* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this r [...]
+| *camel.component.debezium-mysql.configuration.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500 | Long
+| *camel.component.debezium-mysql.configuration.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. | 0 | Long
+| *camel.component.debezium-mysql.configuration.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
+| *camel.component.debezium-mysql.configuration.snapshot-locking-mode* | Controls how long the connector holds onto the global read lock while it is performing a snapshot. The default is 'minimal', which means the connector holds the global read lock (and thus prevents any updates) for just the initial portion of the snapshot while the database schemas and other metadata are being read. The remaining work in a snapshot involves selecting all rows from each table, and this can be done usi [...]
+| *camel.component.debezium-mysql.configuration.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'when_needed' to specify that the connector run a snapshot upon startup whenever it deems it necessary; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initial' except the connector should stop after completing the snapshot and before [...]
+| *camel.component.debezium-mysql.configuration.snapshot-new-tables* | BETA FEATURE: On connector restart, the connector will check if there have been any new tables added to the configuration, and snapshot them. There is presently only two options:'off': Default behavior. Do not snapshot new tables.'parallel': The snapshot of the new tables will occur in parallel to the continued binlog reading of the old tables. When the snapshot completes, an independent binlog reader will begin readi [...]
+| *camel.component.debezium-mysql.configuration.table-blacklist* | Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. | | String
+| *camel.component.debezium-mysql.configuration.table-ignore-builtin* | Flag specifying whether built-in tables should be ignored. | true | Boolean
+| *camel.component.debezium-mysql.configuration.table-whitelist* | The tables for which changes are to be captured | | String
+| *camel.component.debezium-mysql.configuration.time-precision-mode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive_time_microseconds' (the default) like 'adaptive' mode, but TIME fields always use microseconds precision;'adaptive' (deprecated) bases the precision of time, date, and timestamp values on the database column's precision; 'connect' always represents time, date, and timestamp values using Kafka Connect's built-in repres [...]
+| *camel.component.debezium-mysql.configuration.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
| *camel.component.debezium-mysql.enabled* | Whether to enable auto configuration of the debezium-mysql component. This is enabled by default. | | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
index 53648a1..177d497 100644
--- a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
+++ b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
@@ -77,12 +77,12 @@ with the following path and query parameters:
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
| *internalKeyConverter* (consumer) | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
| *internalValueConverter* (consumer) | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface .OffsetCommitPolicy. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
| *offsetCommitTimeoutMs* (consumer) | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000 | long
| *offsetFlushIntervalMs* (consumer) | Interval at which to try committing offsets. The default is 1 minute. | 60000 | long
| *offsetStorage* (consumer) | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
| *offsetStorageFileName* (consumer) | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore | | String
-| *offsetStoragePartitions* (consumer) | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the .KafkaOffsetBackingStore. | | int
+| *offsetStoragePartitions* (consumer) | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | int
| *offsetStorageReplication Factor* (consumer) | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | int
| *offsetStorageTopic* (consumer) | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
@@ -159,61 +159,61 @@ The component supports 57 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-postgres.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
-| *camel.component.debezium-postgres.configuration.column-blacklist* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
+| *camel.component.debezium-postgres.configuration.column-blacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | | String
| *camel.component.debezium-postgres.configuration.connector-class* | The name of the Java class for the connector | | Class
-| *camel.component.debezium-postgres.configuration.database-dbname* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-history-file-filename* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-hostname* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-initial-statements* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-password* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-port* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 5432 | Integer
-| *camel.component.debezium-postgres.configuration.database-server-name* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-sslcert* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-sslfactory* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-sslkey* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-sslmode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | disable | String
-| *camel.component.debezium-postgres.configuration.database-sslpassword* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-sslrootcert* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.database-tcpkeepalive* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | true | Boolean
-| *camel.component.debezium-postgres.configuration.database-user* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.decimal-handling-mode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | precise | String
-| *camel.component.debezium-postgres.configuration.heartbeat-interval-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 0 | Integer
-| *camel.component.debezium-postgres.configuration.heartbeat-topics-prefix* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | __debezium-heartbeat | String
-| *camel.component.debezium-postgres.configuration.hstore-handling-mode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | json | String
-| *camel.component.debezium-postgres.configuration.include-unknown-datatypes* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | false | Boolean
+| *camel.component.debezium-postgres.configuration.database-dbname* | The name of the database the connector should be monitoring | | String
+| *camel.component.debezium-postgres.configuration.database-history-file-filename* | The path to the file that will be used to record the database history | | String
+| *camel.component.debezium-postgres.configuration.database-hostname* | Resolvable hostname or IP address of the Postgres database server. | | String
+| *camel.component.debezium-postgres.configuration.database-initial-statements* | A semicolon separated list of SQL statements to be executed when a JDBC connection to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configurationof session parameters only, but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not as a delimiter. | | String
+| *camel.component.debezium-postgres.configuration.database-password* | Password of the Postgres database user to be used when connecting to the database. | | String
+| *camel.component.debezium-postgres.configuration.database-port* | Port of the Postgres database server. | 5432 | Integer
+| *camel.component.debezium-postgres.configuration.database-server-name* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | | String
+| *camel.component.debezium-postgres.configuration.database-sslcert* | File containing the SSL Certificate for the client. See the Postgres SSL docs for further information | | String
+| *camel.component.debezium-postgres.configuration.database-sslfactory* | A name of class to that creates SSL Sockets. Use org.postgresql.ssl.NonValidatingFactory to disable SSL validation in development environments | | String
+| *camel.component.debezium-postgres.configuration.database-sslkey* | File containing the SSL private key for the client. See the Postgres SSL docs for further information | | String
+| *camel.component.debezium-postgres.configuration.database-sslmode* | Whether to use an encrypted connection to Postgres. Options include'disable' (the default) to use an unencrypted connection; 'require' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify-ca' like 'required' but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or'verif [...]
+| *camel.component.debezium-postgres.configuration.database-sslpassword* | Password to access the client private key from the file specified by 'database.sslkey'. See the Postgres SSL docs for further information | | String
+| *camel.component.debezium-postgres.configuration.database-sslrootcert* | File containing the root certificate(s) against which the server is validated. See the Postgres JDBC SSL docs for further information | | String
+| *camel.component.debezium-postgres.configuration.database-tcpkeepalive* | Enable or disable TCP keep-alive probe to avoid dropping TCP connection | true | Boolean
+| *camel.component.debezium-postgres.configuration.database-user* | Name of the Postgres database user to be used when connecting to the database. | | String
+| *camel.component.debezium-postgres.configuration.decimal-handling-mode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the prec [...]
+| *camel.component.debezium-postgres.configuration.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | Integer
+| *camel.component.debezium-postgres.configuration.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
+| *camel.component.debezium-postgres.configuration.hstore-handling-mode* | Specify how HSTORE columns should be represented in change events, including:'json' represents values as json string'map' (default) represents values using java.util.Map | json | String
+| *camel.component.debezium-postgres.configuration.include-unknown-datatypes* | Specify whether the fields of data type not supported by Debezium should be processed:'false' (the default) omits the fields; 'true' converts the field into an implementation dependent binary representation. | false | Boolean
| *camel.component.debezium-postgres.configuration.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
| *camel.component.debezium-postgres.configuration.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-postgres.configuration.max-batch-size* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 2048 | Integer
-| *camel.component.debezium-postgres.configuration.max-queue-size* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 8192 | Integer
+| *camel.component.debezium-postgres.configuration.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
+| *camel.component.debezium-postgres.configuration.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
| *camel.component.debezium-postgres.configuration.name* | Unique name for the connector. Attempting to register again with the same name will fail. | | String
-| *camel.component.debezium-postgres.configuration.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface <…>.OffsetCommitPolicy. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *camel.component.debezium-postgres.configuration.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
| *camel.component.debezium-postgres.configuration.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000 | Long
| *camel.component.debezium-postgres.configuration.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. | 60000 | Long
| *camel.component.debezium-postgres.configuration.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
| *camel.component.debezium-postgres.configuration.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore | | String
-| *camel.component.debezium-postgres.configuration.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the <…>.KafkaOffsetBackingStore. | | Integer
+| *camel.component.debezium-postgres.configuration.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
| *camel.component.debezium-postgres.configuration.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
| *camel.component.debezium-postgres.configuration.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-postgres.configuration.plugin-name* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | decoderbufs | String
-| *camel.component.debezium-postgres.configuration.poll-interval-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 500 | Long
-| *camel.component.debezium-postgres.configuration.schema-blacklist* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.schema-refresh-mode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | columns_diff | String
-| *camel.component.debezium-postgres.configuration.schema-whitelist* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.slot-name* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | debezium | String
+| *camel.component.debezium-postgres.configuration.plugin-name* | The name of the Postgres logical decoding plugin installed on the server. Supported values are 'decoderbufs' and 'wal2json'. Defaults to 'decoderbufs'. | decoderbufs | String
+| *camel.component.debezium-postgres.configuration.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500 | Long
+| *camel.component.debezium-postgres.configuration.schema-blacklist* | Description is not available here, please check Debezium website for corresponding key 'schema.blacklist' description. | | String
+| *camel.component.debezium-postgres.configuration.schema-refresh-mode* | Specify the conditions that trigger a refresh of the in-memory schema for a table. 'columns_diff' (the default) is the safest mode, ensuring the in-memory schema stays in-sync with the database table's schema at all times. 'columns_diff_exclude_unchanged_toast' instructs the connector to refresh the in-memory schema cache if there is a discrepancy between it and the schema derived from the incoming message, unless [...]
+| *camel.component.debezium-postgres.configuration.schema-whitelist* | The schemas for which events should be captured | | String
+| *camel.component.debezium-postgres.configuration.slot-name* | The name of the Postgres logical decoding slot created for streaming changes from a plugin.Defaults to 'debezium | debezium | String
| *camel.component.debezium-postgres.configuration.slot-stream-params* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.snapshot-custom-class* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.snapshot-delay-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 0 | Long
-| *camel.component.debezium-postgres.configuration.snapshot-fetch-size* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | Integer
-| *camel.component.debezium-postgres.configuration.snapshot-lock-timeout-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 10000 | Long
-| *camel.component.debezium-postgres.configuration.snapshot-mode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | initial | String
-| *camel.component.debezium-postgres.configuration.snapshot-select-statement-overrides* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.status-update-interval-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 10000 | Integer
-| *camel.component.debezium-postgres.configuration.table-blacklist* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.table-whitelist* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.configuration.time-precision-mode* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | adaptive | String
-| *camel.component.debezium-postgres.configuration.tombstones-on-delete* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | false | Boolean
-| *camel.component.debezium-postgres.configuration.topic-selection-strategy* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | topic_per_table | String
-| *camel.component.debezium-postgres.configuration.xmin-fetch-interval-ms* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | 0 | Long
+| *camel.component.debezium-postgres.configuration.snapshot-custom-class* | When 'snapshot.mode' is set as custom, this setting must be set to specify a fully qualified class name to load (via the default class loader).This class must implement the 'Snapshotter' interface and is called on each app boot to determine whether to do a snapshot and how to build queries. | | String
+| *camel.component.debezium-postgres.configuration.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. | 0 | Long
+| *camel.component.debezium-postgres.configuration.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
+| *camel.component.debezium-postgres.configuration.snapshot-lock-timeout-ms* | The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds | 10000 | Long
+| *camel.component.debezium-postgres.configuration.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'always' to specify that the connector run a snapshot each time it starts up; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initial' except the connector should stop after completing the snapshot and before it would normally start [...]
+| *camel.component.debezium-postgres.configuration.snapshot-select-statement-overrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME). Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.[DB_NAME].[TABLE_NAME]'. The value of those properties is the select statement to use when retrieving data from the specific table duri [...]
+| *camel.component.debezium-postgres.configuration.status-update-interval-ms* | Frequency in milliseconds for sending replication connection status updates to the server. Defaults to 10 seconds (10000 ms). | 10000 | Integer
+| *camel.component.debezium-postgres.configuration.table-blacklist* | Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. | | String
+| *camel.component.debezium-postgres.configuration.table-whitelist* | The tables for which changes are to be captured | | String
+| *camel.component.debezium-postgres.configuration.time-precision-mode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations [...]
+| *camel.component.debezium-postgres.configuration.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
+| *camel.component.debezium-postgres.configuration.topic-selection-strategy* | How events received from the DB should be placed on topics. Options include'table' (the default) each DB table will have a separate Kafka topic; 'schema' there will be one Kafka topic per DB schema; events from multiple topics belonging to the same schema will be placed on the same topic | topic_per_table | String
+| *camel.component.debezium-postgres.configuration.xmin-fetch-interval-ms* | Specify how often (in ms) the xmin will be fetched from the replication slot. This xmin value is exposed by the slot which gives a lower bound of where a new replication slot could start from. The lower the value, the more likely this value is to be the current 'true' value, but the bigger the performance cost. The bigger the value, the less likely this value is to be the current 'true' value, but the lower the [...]
| *camel.component.debezium-postgres.enabled* | Whether to enable auto configuration of the debezium-postgres component. This is enabled by default. | | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/platforms/spring-boot/components-starter/camel-debezium-mysql-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumMySqlComponentConfiguration.java b/platforms/spring-boot/components-starter/camel-debezium-mysql-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumMySqlComponentConfiguration.java
index 8c9c522..409fd6d 100644
--- a/platforms/spring-boot/components-starter/camel-debezium-mysql-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumMySqlComponentConfiguration.java
+++ b/platforms/spring-boot/components-starter/camel-debezium-mysql-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumMySqlComponentConfiguration.java
@@ -68,553 +68,386 @@ public class DebeziumMySqlComponentConfiguration
public static class MySqlConnectorEmbeddedDebeziumConfigurationNestedConfiguration {
public static final Class CAMEL_NESTED_CLASS = org.apache.camel.component.debezium.configuration.MySqlConnectorEmbeddedDebeziumConfiguration.class;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Controls how long the connector holds onto the global read lock while
+ * it is performing a snapshot. The default is 'minimal', which means
+ * the connector holds the global read lock (and thus prevents any
+ * updates) for just the initial portion of the snapshot while the
+ * database schemas and other metadata are being read. The remaining
+ * work in a snapshot involves selecting all rows from each table, and
+ * this can be done using the snapshot process' REPEATABLE READ
+ * transaction even when the lock is no longer held and other operations
+ * are updating the database. However, in some cases it may be desirable
+ * to block all writes for the entire duration of the snapshot; in such
+ * cases set this property to 'extended'. Using a value of 'none' will
+ * prevent the connector from acquiring any table locks during the
+ * snapshot process. This mode can only be used in combination with
+ * snapshot.mode values of 'schema_only' or 'schema_only_recovery' and
+ * is only safe to use if no schema changes are happening while the
+ * snapshot is taken.
*/
private String snapshotLockingMode = "minimal";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'column.blacklist' description.
*/
private String columnBlacklist;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'table.blacklist' description.
*/
private String tableBlacklist;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Whether the connector should publish changes in the database schema
+ * to a Kafka topic with the same name as the database server ID. Each
+ * schema change will be recorded using a key that contains the database
+ * name and whose value includes the DDL statement(s).The default is
+ * 'true'. This is independent of how the connector internally records
+ * database history.
*/
private Boolean includeSchemaChanges = true;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The source UUIDs used to include GTID ranges when determine the
+ * starting position in the MySQL server's binlog.
*/
private String gtidSourceIncludes;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * JDBC Driver class name used to connect to the MySQL database server.
*/
private String databaseJdbcDriver = "class com.mysql.cj.jdbc.Driver";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The number of milliseconds to wait while polling for persisted data
+ * during recovery.
*/
private Integer databaseHistoryKafkaRecoveryPollIntervalMs = 100;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Frequency in milliseconds to wait for new change events to appear
+ * after receiving no events. Defaults to 500ms.
*/
private Long pollIntervalMs = 500L;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * A semicolon separated list of SQL statements to be executed when a
+ * JDBC connection (not binlog reading connection) to the database is
+ * established. Note that the connector may establish JDBC connections
+ * at its own discretion, so this should typically be used for
+ * configuration of session parameters only,but not for executing DML
+ * statements. Use doubled semicolon (';;') to use a semicolon as a
+ * character and not as a delimiter.
*/
private String databaseInitialStatements;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The prefix that is used to name heartbeat topics.Defaults to
+ * __debezium-heartbeat.
*/
private String heartbeatTopicsPrefix = "__debezium-heartbeat";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The size of a look-ahead buffer used by the binlog reader to decide
+ * whether the transaction in progress is going to be committed or
+ * rolled back. Use 0 to disable look-ahead buffering. Defaults to 0
+ * (i.e. buffering is disabled).
*/
private Integer binlogBufferSize = 0;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The maximum number of records that should be loaded into memory while
+ * performing a snapshot
*/
private Integer snapshotFetchSize;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Name of the MySQL database user to be used when connecting to the
+ * database.
*/
private String databaseUser;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The source UUIDs used to exclude GTID ranges when determine the
+ * starting position in the MySQL server's binlog.
*/
private String gtidSourceExcludes;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * A list of host/port pairs that the connector will use for
+ * establishing the initial connection to the Kafka cluster for
+ * retrieving database schema history previously stored by the
+ * connector. This should point to the same Kafka cluster used by the
+ * Kafka Connect process.
*/
private String databaseHistoryKafkaBootstrapServers;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Location of the Java keystore file containing an application
+ * process's own certificate and private key.
*/
private String databaseSslKeystore;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Length of an interval in milli-seconds in in which the connector
+ * periodically sends heartbeat messages to a heartbeat topic. Use 0 to
+ * disable heartbeat messages. Disabled by default.
*/
private Integer heartbeatIntervalMs = 0;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Password to unlock the keystore file (store password) specified by
+ * 'ssl.trustore' configuration property or the
+ * 'javax.net.ssl.trustStore' system or JVM property.
*/
private String databaseSslTruststorePassword;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Specify how binlog events that belong to a table missing from
+ * internal schema representation (i.e. internal representation is not
+ * consistent with database) should be handled, including:'fail' (the
+ * default) an exception indicating the problematic event and its binlog
+ * position is raised, causing the connector to be stopped; 'warn' the
+ * problematic event and its binlog position will be logged and the
+ * event will be skipped;'ignore' the problematic event will be skipped.
*/
private String inconsistentSchemaHandlingMode = "fail";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * MySQL allows user to insert year value as either 2-digit or 4-digit.
+ * In case of two digit the value is automatically mapped into 1970 -
+ * 2069.false - delegates the implicit conversion to the databasetrue -
+ * (the default) Debezium makes the conversion
*/
private Boolean enableTimeAdjuster = true;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * If set to 'latest', when connector sees new GTID, it will start
+ * consuming gtid channel from the server latest executed gtid position.
+ * If 'earliest' connector starts reading channel from first available
+ * (not purged) gtid position on the server.
*/
private String gtidNewChannelPosition = "latest";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * MySQL DDL statements can be parsed in different ways:'legacy' parsing
+ * is creating a TokenStream and comparing token by token with an
+ * expected values.The decisions are made by matched token
+ * values.'antlr' (the default) uses generated parser from MySQL grammar
+ * using ANTLR v4 tool which use ALL(*) algorithm for parsing.This
+ * parser creates a parsing tree for DDL statement, then walks trough it
+ * and apply changes by node types in parsed tree.
*/
private String ddlParserMode = "antlr";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Password of the MySQL database user to be used when connecting to the
+ * database.
*/
private String databasePassword;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Controls what DDL will Debezium store in database history.By default
+ * (false) Debezium will store all incoming DDL statements. If set to
+ * truethen only DDL that manipulates a monitored table will be stored.
*/
private Boolean databaseHistoryStoreOnlyMonitoredTablesDdl = false;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * If set to true, we will only produce DML events into Kafka for
+ * transactions that were written on mysql servers with UUIDs matching
+ * the filters defined by the gtid.source.includes or
+ * gtid.source.excludes configuration options, if they are specified.
*/
private Boolean gtidSourceFilterDmlEvents = true;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'database.blacklist' description.
*/
private String databaseBlacklist;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Maximum size of each batch of source records. Defaults to 2048.
*/
private Integer maxBatchSize = 2048;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Whether a separate thread should be used to ensure the connection is
+ * kept alive.
*/
private Boolean connectKeepAlive = true;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The name of the DatabaseHistory class that should be used to store
+ * and recover database schema changes. The configuration properties for
+ * the history are prefixed with the 'database.history.' string.
*/
private String databaseHistory = "io.debezium.relational.history.FileDatabaseHistory";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The criteria for running a snapshot upon startup of the connector.
+ * Options include: 'when_needed' to specify that the connector run a
+ * snapshot upon startup whenever it deems it necessary; 'initial' (the
+ * default) to specify the connector can run a snapshot only when no
+ * offsets are available for the logical server name; 'initial_only'
+ * same as 'initial' except the connector should stop after completing
+ * the snapshot and before it would normally read the binlog; and'never'
+ * to specify the connector should never run a snapshot and that upon
+ * first startup the connector should read from the beginning of the
+ * binlog. The 'never' mode should be used with care, and only when the
+ * binlog is known to contain all history.
*/
private String snapshotMode = "initial";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Maximum time in milliseconds to wait after trying to connect to the
+ * database before timing out.
*/
private Integer connectTimeoutMs = 30000;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Maximum size of the queue for change events read from the database
+ * log but not yet recorded or forwarded. Defaults to 8192, and should
+ * always be larger than the maximum batch size.
*/
private Integer maxQueueSize = 8192;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The name of the topic for the database schema history
*/
private String databaseHistoryKafkaTopic;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The number of milliseconds to delay before a snapshot will begin.
*/
private Long snapshotDelayMs = 0L;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The number of attempts in a row that no data are returned from Kafka
+ * before recover completes. The maximum amount of time to wait after
+ * receiving no data is (recovery.attempts) x
+ * (recovery.poll.interval.ms).
*/
private Integer databaseHistoryKafkaRecoveryAttempts = 100;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The tables for which changes are to be captured
*/
private String tableWhitelist;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Whether delete operations should be represented by a delete event and
+ * a subsquenttombstone event (true) or only by a delete event (false).
+ * Emitting the tombstone event (the default behavior) allows Kafka to
+ * completely delete all events pertaining to the given key once the
+ * source record got deleted.
*/
private Boolean tombstonesOnDelete = false;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Specify how DECIMAL and NUMERIC columns should be represented in
+ * change events, including:'precise' (the default) uses
+ * java.math.BigDecimal to represent values, which are encoded in the
+ * change events using a binary representation and Kafka Connect's
+ * 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to
+ * represent values; 'double' represents values using Java's 'double',
+ * which may not offer the precision but will be far easier to use in
+ * consumers.
*/
private String decimalHandlingMode = "precise";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * BETA FEATURE: On connector restart, the connector will check if there
+ * have been any new tables added to the configuration, and snapshot
+ * them. There is presently only two options:'off': Default behavior. Do
+ * not snapshot new tables.'parallel': The snapshot of the new tables
+ * will occur in parallel to the continued binlog reading of the old
+ * tables. When the snapshot completes, an independent binlog reader
+ * will begin reading the events for the new tables until it catches up
+ * to present time. At this point, both old and new binlog readers will
+ * be momentarily halted and new binlog reader will start that will read
+ * the binlog for all configured tables. The parallel binlog reader will
+ * have a configured server id of 10000 + the primary binlog reader's
+ * server id.
*/
private String snapshotNewTables = "off";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Controls the action Debezium will take when it meets a DDL statement
+ * in binlog, that it cannot parse.By default the connector will stop
+ * operating but by changing the setting it can ignore the statements
+ * which it cannot parse. If skipping is enabled then Debezium can miss
+ * metadata changes.
*/
private Boolean databaseHistorySkipUnparseableDdl = false;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Flag specifying whether built-in tables should be ignored.
*/
private Boolean tableIgnoreBuiltin = true;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The databases for which changes are to be captured
*/
private String databaseWhitelist;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * The path to the file that will be used to record the database history
*/
private String databaseHistoryFileFilename;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Specify how BIGINT UNSIGNED columns should be represented in change
+ * events, including:'precise' uses java.math.BigDecimal to represent
+ * values, which are encoded in the change events using a binary
+ * representation and Kafka Connect's
+ * 'org.apache.kafka.connect.data.Decimal' type; 'long' (the default)
+ * represents values using Java's 'long', which may not offer the
+ * precision but will be far easier to use in consumers.
*/
private String bigintUnsignedHandlingMode = "long";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * A numeric ID of this database client, which must be unique across all
+ * currently-running database processes in the cluster. This connector
+ * joins the MySQL database cluster as another server (with this unique
+ * ID) so it can read the binlog. By default, a random number is
+ * generated between 5400 and 6400.
*/
private Long databaseServerId;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Specify how failures during deserialization of binlog events (i.e.
+ * when encountering a corrupted event) should be handled,
+ * including:'fail' (the default) an exception indicating the
+ * problematic event and its binlog position is raised, causing the
+ * connector to be stopped; 'warn' the problematic event and its binlog
+ * position will be logged and the event will be skipped;'ignore' the
+ * problematic event will be skipped.
*/
private String eventDeserializationFailureHandlingMode = "fail";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Time, date, and timestamps can be represented with different kinds of
+ * precisions, including:'adaptive_time_microseconds' (the default) like
+ * 'adaptive' mode, but TIME fields always use microseconds
+ * precision;'adaptive' (deprecated) bases the precision of time, date,
+ * and timestamp values on the database column's precision; 'connect'
+ * always represents time, date, and timestamp values using Kafka
+ * Connect's built-in representations for Time, Date, and Timestamp,
+ * which uses millisecond precision regardless of the database columns'
+ * precision.
*/
private String timePrecisionMode = "adaptive_time_microseconds";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Unique name that identifies the database server and all recorded
+ * offsets, and that is used as a prefix for all schemas and topics.
+ * Each distinct installation should have a separate namespace and be
+ * monitored by at most one Debezium connector.
*/
private String databaseServerName;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Port of the MySQL database server.
*/
private Integer databasePort = 3306;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Location of the Java truststore file containing the collection of CA
+ * certificates trusted by this application process (trust store).
*/
private String databaseSslTruststore;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Whether to use an encrypted connection to MySQL. Options
+ * include'disabled' (the default) to use an unencrypted connection;
+ * 'preferred' to establish a secure (encrypted) connection if the
+ * server supports secure connections, but fall back to an unencrypted
+ * connection otherwise; 'required' to use a secure (encrypted)
+ * connection, and fail if one cannot be established; 'verify_ca' like
+ * 'required' but additionally verify the server TLS certificate against
+ * the configured Certificate Authority (CA) certificates, or fail if no
+ * valid matching CA certificates are found; or'verify_identity' like
+ * 'verify_ca' but additionally verify that the server certificate
+ * matches the host to which the connection is attempted.
*/
private String databaseSslMode = "disabled";
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Password to access the private key from the keystore file specified
+ * by 'ssl.keystore' configuration property or the
+ * 'javax.net.ssl.keyStore' system or JVM property. This password is
+ * used to unlock the keystore file (store password), and to decrypt the
+ * private key stored in the keystore (key password).
*/
private String databaseSslKeystorePassword;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Resolvable hostname or IP address of the MySQL database server.
*/
private String databaseHostname;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Only relevant if parallel snapshotting is configured. During parallel
+ * snapshotting, multiple (4) connections open to the database client,
+ * and they each need their own unique connection ID. This offset is
+ * used to generate those IDs from the base configured cluster ID.
*/
private Long databaseServerIdOffset = 10000L;
/**
- * Whether the connector should include the original SQL query that
- * generated the change event. Note: This option requires MySQL be
- * configured with the binlog_rows_query_log_events option set to ON.
- * Query will not be present for events generated from snapshot.
- * WARNING: Enabling this option may expose tables or fields explicitly
- * blacklisted or masked by including the original SQL statement in the
- * change event. For this reason the default value is 'false'.
+ * Interval in milliseconds to wait for connection checking if keep
+ * alive thread is used.
*/
private Long connectKeepAliveIntervalMs = 60000L;
/**
@@ -660,7 +493,7 @@ public class DebeziumMySqlComponentConfiguration
* The name of the Java class of the commit policy. It defines when
* offsets commit has to be triggered based on the number of events
* processed and the time elapsed since the last commit. This class must
- * implement the interface <…>.OffsetCommitPolicy. The default is a
+ * implement the interface 'OffsetCommitPolicy'. The default is a
* periodic commit policy based upon time intervals.
*/
private String offsetCommitPolicy = "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy";
@@ -677,8 +510,7 @@ public class DebeziumMySqlComponentConfiguration
private Long offsetCommitTimeoutMs = 5000L;
/**
* The number of partitions used when creating the offset storage topic.
- * Required when offset.storage is set to the
- * <…>.KafkaOffsetBackingStore.
+ * Required when offset.storage is set to the 'KafkaOffsetBackingStore'.
*/
private Integer offsetStoragePartitions;
/**
diff --git a/platforms/spring-boot/components-starter/camel-debezium-postgres-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumPostgresComponentConfiguration.java b/platforms/spring-boot/components-starter/camel-debezium-postgres-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumPostgresComponentConfiguration.java
index b82f9e2..40a2127 100644
--- a/platforms/spring-boot/components-starter/camel-debezium-postgres-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumPostgresComponentConfiguration.java
+++ b/platforms/spring-boot/components-starter/camel-debezium-postgres-starter/src/main/java/org/apache/camel/component/debezium/springboot/DebeziumPostgresComponentConfiguration.java
@@ -68,255 +68,281 @@ public class DebeziumPostgresComponentConfiguration
public static class PostgresConnectorEmbeddedDebeziumConfigurationNestedConfiguration {
public static final Class CAMEL_NESTED_CLASS = org.apache.camel.component.debezium.configuration.PostgresConnectorEmbeddedDebeziumConfiguration.class;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * When 'snapshot.mode' is set as custom, this setting must be set to
+ * specify a fully qualified class name to load (via the default class
+ * loader).This class must implement the 'Snapshotter' interface and is
+ * called on each app boot to determine whether to do a snapshot and how
+ * to build queries.
*/
private String snapshotCustomClass;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Maximum size of the queue for change events read from the database
+ * log but not yet recorded or forwarded. Defaults to 8192, and should
+ * always be larger than the maximum batch size.
*/
private Integer maxQueueSize = 8192;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The name of the Postgres logical decoding slot created for streaming
+ * changes from a plugin.Defaults to 'debezium
*/
private String slotName = "debezium";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Specify how HSTORE columns should be represented in change events,
+ * including:'json' represents values as json string'map' (default)
+ * represents values using java.util.Map
*/
private String hstoreHandlingMode = "json";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'column.blacklist' description.
*/
private String columnBlacklist;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The number of milliseconds to delay before a snapshot will begin.
*/
private Long snapshotDelayMs = 0L;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'schema.blacklist' description.
*/
private String schemaBlacklist;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Description is not available here, please check Debezium website for
+ * corresponding key 'table.blacklist' description.
*/
private String tableBlacklist;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Specify the conditions that trigger a refresh of the in-memory schema
+ * for a table. 'columns_diff' (the default) is the safest mode,
+ * ensuring the in-memory schema stays in-sync with the database table's
+ * schema at all times. 'columns_diff_exclude_unchanged_toast' instructs
+ * the connector to refresh the in-memory schema cache if there is a
+ * discrepancy between it and the schema derived from the incoming
+ * message, unless unchanged TOASTable data fully accounts for the
+ * discrepancy. This setting can improve connector performance
+ * significantly if there are frequently-updated tables that have
+ * TOASTed data that are rarely part of these updates. However, it is
+ * possible for the in-memory schema to become outdated if TOASTable
+ * columns are dropped from the table.
*/
private String schemaRefreshMode = "columns_diff";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The tables for which changes are to be captured
*/
private String tableWhitelist;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * How events received from the DB should be placed on topics. Options
+ * include'table' (the default) each DB table will have a separate Kafka
+ * topic; 'schema' there will be one Kafka topic per DB schema; events
+ * from multiple topics belonging to the same schema will be placed on
+ * the same topic
*/
private String topicSelectionStrategy = "topic_per_table";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Whether delete operations should be represented by a delete event and
+ * a subsquenttombstone event (true) or only by a delete event (false).
+ * Emitting the tombstone event (the default behavior) allows Kafka to
+ * completely delete all events pertaining to the given key once the
+ * source record got deleted.
*/
private Boolean tombstonesOnDelete = false;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Whether to use an encrypted connection to Postgres. Options
+ * include'disable' (the default) to use an unencrypted connection;
+ * 'require' to use a secure (encrypted) connection, and fail if one
+ * cannot be established; 'verify-ca' like 'required' but additionally
+ * verify the server TLS certificate against the configured Certificate
+ * Authority (CA) certificates, or fail if no valid matching CA
+ * certificates are found; or'verify-full' like 'verify-ca' but
+ * additionally verify that the server certificate matches the host to
+ * which the connection is attempted.
*/
private String databaseSslmode = "disable";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Specify how DECIMAL and NUMERIC columns should be represented in
+ * change events, including:'precise' (the default) uses
+ * java.math.BigDecimal to represent values, which are encoded in the
+ * change events using a binary representation and Kafka Connect's
+ * 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to
+ * represent values; 'double' represents values using Java's 'double',
+ * which may not offer the precision but will be far easier to use in
+ * consumers.
*/
private String decimalHandlingMode = "precise";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * File containing the SSL Certificate for the client. See the Postgres
+ * SSL docs for further information
*/
private String databaseSslcert;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Frequency in milliseconds to wait for new change events to appear
+ * after receiving no events. Defaults to 500ms.
*/
private Long pollIntervalMs = 500L;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * A semicolon separated list of SQL statements to be executed when a
+ * JDBC connection to the database is established. Note that the
+ * connector may establish JDBC connections at its own discretion, so
+ * this should typically be used for configurationof session parameters
+ * only, but not for executing DML statements. Use doubled semicolon
+ * (';;') to use a semicolon as a character and not as a delimiter.
*/
private String databaseInitialStatements;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The prefix that is used to name heartbeat topics.Defaults to
+ * __debezium-heartbeat.
*/
private String heartbeatTopicsPrefix = "__debezium-heartbeat";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * A name of class to that creates SSL Sockets. Use
+ * org.postgresql.ssl.NonValidatingFactory to disable SSL validation in
+ * development environments
*/
private String databaseSslfactory;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Frequency in milliseconds for sending replication connection status
+ * updates to the server. Defaults to 10 seconds (10000 ms).
*/
private Integer statusUpdateIntervalMs = 10000;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The maximum number of records that should be loaded into memory while
+ * performing a snapshot
*/
private Integer snapshotFetchSize;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The maximum number of millis to wait for table locks at the beginning
+ * of a snapshot. If locks cannot be acquired in this time frame, the
+ * snapshot will be aborted. Defaults to 10 seconds
*/
private Long snapshotLockTimeoutMs = 10000L;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Enable or disable TCP keep-alive probe to avoid dropping TCP
+ * connection
*/
private Boolean databaseTcpkeepalive = true;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The path to the file that will be used to record the database history
*/
private String databaseHistoryFileFilename;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The name of the database the connector should be monitoring
*/
private String databaseDbname;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Name of the Postgres database user to be used when connecting to the
+ * database.
*/
private String databaseUser;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * File containing the SSL private key for the client. See the Postgres
+ * SSL docs for further information
*/
private String databaseSslkey;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * This property contains a comma-separated list of fully-qualified
+ * tables (DB_NAME.TABLE_NAME). Select statements for the individual
+ * tables are specified in further configuration properties, one for
+ * each table, identified by the id
+ * 'snapshot.select.statement.overrides.[DB_NAME].[TABLE_NAME]'. The
+ * value of those properties is the select statement to use when
+ * retrieving data from the specific table during snapshotting. A
+ * possible use case for large append-only tables is setting a specific
+ * point where to start (resume) snapshotting, in case a previous
+ * snapshotting was interrupted.
*/
private String snapshotSelectStatementOverrides;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Specify how often (in ms) the xmin will be fetched from the
+ * replication slot. This xmin value is exposed by the slot which gives
+ * a lower bound of where a new replication slot could start from. The
+ * lower the value, the more likely this value is to be the current
+ * 'true' value, but the bigger the performance cost. The bigger the
+ * value, the less likely this value is to be the current 'true' value,
+ * but the lower the performance penalty. The default is set to 0 ms,
+ * which disables tracking xmin.
*/
private Long xminFetchIntervalMs = 0L;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Time, date, and timestamps can be represented with different kinds of
+ * precisions, including:'adaptive' (the default) bases the precision of
+ * time, date, and timestamp values on the database column's precision;
+ * 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields
+ * always use microseconds precision;'connect' always represents time,
+ * date, and timestamp values using Kafka Connect's built-in
+ * representations for Time, Date, and Timestamp, which uses millisecond
+ * precision regardless of the database columns' precision .
*/
private String timePrecisionMode = "adaptive";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Unique name that identifies the database server and all recorded
+ * offsets, and that is used as a prefix for all schemas and topics.
+ * Each distinct installation should have a separate namespace and be
+ * monitored by at most one Debezium connector.
*/
private String databaseServerName;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Length of an interval in milli-seconds in in which the connector
+ * periodically sends heartbeat messages to a heartbeat topic. Use 0 to
+ * disable heartbeat messages. Disabled by default.
*/
private Integer heartbeatIntervalMs = 0;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The name of the Postgres logical decoding plugin installed on the
+ * server. Supported values are 'decoderbufs' and 'wal2json'. Defaults
+ * to 'decoderbufs'.
*/
private String pluginName = "decoderbufs";
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Port of the Postgres database server.
*/
private Integer databasePort = 5432;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Password to access the client private key from the file specified by
+ * 'database.sslkey'. See the Postgres SSL docs for further information
*/
private String databaseSslpassword;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The schemas for which events should be captured
*/
private String schemaWhitelist;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Specify whether the fields of data type not supported by Debezium
+ * should be processed:'false' (the default) omits the fields; 'true'
+ * converts the field into an implementation dependent binary
+ * representation.
*/
private Boolean includeUnknownDatatypes = false;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Resolvable hostname or IP address of the Postgres database server.
*/
private String databaseHostname;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Password of the Postgres database user to be used when connecting to
+ * the database.
*/
private String databasePassword;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * File containing the root certificate(s) against which the server is
+ * validated. See the Postgres JDBC SSL docs for further information
*/
private String databaseSslrootcert;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * Maximum size of each batch of source records. Defaults to 2048.
*/
private Integer maxBatchSize = 2048;
/**
- * Any optional parameters used by logical decoding plugin. Semi-colon
- * separated. E.g.
- * 'add-tables=public.table,public.table2;include-lsn=true'
+ * The criteria for running a snapshot upon startup of the connector.
+ * Options include: 'always' to specify that the connector run a
+ * snapshot each time it starts up; 'initial' (the default) to specify
+ * the connector can run a snapshot only when no offsets are available
+ * for the logical server name; 'initial_only' same as 'initial' except
+ * the connector should stop after completing the snapshot and before it
+ * would normally start emitting changes;'never' to specify the
+ * connector should never run a snapshot and that upon first startup the
+ * connector should read from the last position (LSN) recorded by the
+ * server; and'custom' to specify a custom class with
+ * 'snapshot.custom_class' which will be loaded and used to determine
+ * the snapshot, see docs for more details.
*/
private String snapshotMode = "initial";
/**
@@ -358,7 +384,7 @@ public class DebeziumPostgresComponentConfiguration
* The name of the Java class of the commit policy. It defines when
* offsets commit has to be triggered based on the number of events
* processed and the time elapsed since the last commit. This class must
- * implement the interface <…>.OffsetCommitPolicy. The default is a
+ * implement the interface 'OffsetCommitPolicy'. The default is a
* periodic commit policy based upon time intervals.
*/
private String offsetCommitPolicy = "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy";
@@ -375,8 +401,7 @@ public class DebeziumPostgresComponentConfiguration
private Long offsetCommitTimeoutMs = 5000L;
/**
* The number of partitions used when creating the offset storage topic.
- * Required when offset.storage is set to the
- * <…>.KafkaOffsetBackingStore.
+ * Required when offset.storage is set to the 'KafkaOffsetBackingStore'.
*/
private Integer offsetStoragePartitions;
/**