This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
commit c35012c40af666bb65df9226bdc9636d5f132512 Author: Claus Ibsen <[email protected]> AuthorDate: Thu Jul 2 14:11:17 2026 +0200 Regen --- .../src/main/docs/debezium-oracle.json | 180 +++++++++++++-------- .../src/main/docs/debezium-postgres.json | 23 ++- .../src/main/docs/debezium-sqlserver.json | 23 ++- .../ROOT/pages/starters/debezium-oracle.adoc | 37 +++-- .../ROOT/pages/starters/debezium-postgres.adoc | 7 +- .../ROOT/pages/starters/debezium-sqlserver.adoc | 7 +- 6 files changed, 189 insertions(+), 88 deletions(-) diff --git a/components-starter/camel-debezium-oracle-starter/src/main/docs/debezium-oracle.json b/components-starter/camel-debezium-oracle-starter/src/main/docs/debezium-oracle.json index 519d1079472..bd83a5f9a23 100644 --- a/components-starter/camel-debezium-oracle-starter/src/main/docs/debezium-oracle.json +++ b/components-starter/camel-debezium-oracle-starter/src/main/docs/debezium-oracle.json @@ -53,6 +53,13 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": false }, + { + "name": "camel.component.debezium-oracle.capture-mode", + "type": "java.lang.String", + "description": "Specifies the capture mode used to capture streaming changes from Oracle'primary' (the default) captures changes from the primary, specified by database. configurations, 'physical_standby' captures changes from a read-only physical standby, specified by secondary. configurations.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": "primary" + }, { "name": "camel.component.debezium-oracle.column-exclude-list", "type": "java.lang.String", @@ -323,32 +330,18 @@ "defaultValue": 10000 }, { - "name": "camel.component.debezium-oracle.log-mining-batch-size-default", + "name": "camel.component.debezium-oracle.log-mining-buffer-deferred-transaction-retention-ms", "type": "java.lang.Long", - "description": "The starting SCN interval size that the connector will use for reading data from redo\/archive logs.", + "description": "Duration in milliseconds to retain deferred transaction metadata for transactions that never emit a DML event. By default, deferred transaction metadata is retained for 24 hours. This is independent of log.mining.transaction.retention.ms which governs cached transactions with events. The option is a long type.", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 20000 + "defaultValue": 86400000 }, { - "name": "camel.component.debezium-oracle.log-mining-batch-size-increment", - "type": "java.lang.Long", - "description": "Active batch size will be also increased\/decreased by this amount for tuning connector throughput when needed.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 20000 - }, - { - "name": "camel.component.debezium-oracle.log-mining-batch-size-max", - "type": "java.lang.Long", - "description": "The maximum SCN interval size that this connector will use when reading from redo\/archive logs.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 100000 - }, - { - "name": "camel.component.debezium-oracle.log-mining-batch-size-min", - "type": "java.lang.Long", - "description": "The minimum SCN interval size that this connector will try to read from redo\/archive logs.", + "name": "camel.component.debezium-oracle.log-mining-buffer-deferred-transaction-start", + "type": "java.lang.Boolean", + "description": "Controls whether transaction start events are deferred when using buffered LogMiner. When enabled, transaction start events are stored in a lightweight metadata map. Transactions are only promoted to the transaction cache when a DML event is observed. The mining window is not pinned by transactions, allowing a block-by-block sliding window.", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 1000 + "defaultValue": false }, { "name": "camel.component.debezium-oracle.log-mining-buffer-drop-on-stop", @@ -429,10 +422,45 @@ "description": "Specifies the XML configuration for the Infinispan 'transactions' cache", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration" }, + { + "name": "camel.component.debezium-oracle.log-mining-buffer-memory-legacy-transaction-start", + "type": "java.lang.Boolean", + "description": "Controls whether transaction start events are deferred when using buffered LogMiner. When enabled, transaction start events are stored in a lightweight metadata map. Transactions are only promoted to the transaction cache when a DML event is observed. The mining window is not pinned by transactions, allowing a block-by-block sliding window.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": false + }, + { + "name": "camel.component.debezium-oracle.log-mining-buffer-track-client-id", + "type": "java.lang.Boolean", + "description": "This controls whether the 'CLIENT_ID' column values are tracked. When set to true (the default), the 'CLIENT_ID' values are buffered and provided in events when available. When set to false, the 'CLIENT_ID' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": true + }, + { + "name": "camel.component.debezium-oracle.log-mining-buffer-track-commit-timestamp", + "type": "java.lang.Boolean", + "description": "This controls whether the 'COMMIT_TIMESTAMP' column values are tracked. When set to true (the default), the 'COMMIT_TIMESTAMP' values are buffered and provided in events when available. When set to false, the 'COMMIT_TIMESTAMP' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": true + }, { "name": "camel.component.debezium-oracle.log-mining-buffer-track-rs-id", "type": "java.lang.Boolean", - "description": "This controls whether the 'RS_ID' column values are tracked. When set to true (the default), the 'RS_ID' values are buffered and provided in events when available. When set to false, the 'RS_ID' values are not buffered and can reduce the memory footprint.", + "description": "This controls whether the 'RS_ID' column values are tracked. When set to true (the default), the 'RS_ID' values are buffered and provided in events when available. When set to false, the 'RS_ID' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": true + }, + { + "name": "camel.component.debezium-oracle.log-mining-buffer-track-start-timestamp", + "type": "java.lang.Boolean", + "description": "This controls whether the 'START_TIMESTAMP' column values are tracked. When set to true (the default), the 'START_TIMESTAMP' values are buffered and provided in events when available. When set to false, the 'START_TIMESTAMP' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": true + }, + { + "name": "camel.component.debezium-oracle.log-mining-buffer-track-username", + "type": "java.lang.Boolean", + "description": "This controls whether the 'USERNAME' column values are tracked. When set to true (the default), the 'USERNAME' values are buffered and provided in events when available. When set to false, the 'USERNAME' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth.", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": true }, @@ -476,6 +504,13 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": false }, + { + "name": "camel.component.debezium-oracle.log-mining-log-count-min", + "type": "java.lang.Integer", + "description": "Specifies the minimum number of logs to mine per redo thread. Setting this to 0 disables the cap, and all available logs are mined in a single pass.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": 2 + }, { "name": "camel.component.debezium-oracle.log-mining-path-dictionary", "type": "java.lang.String", @@ -489,10 +524,17 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": "none" }, + { + "name": "camel.component.debezium-oracle.log-mining-read-only", + "type": "java.lang.Boolean", + "description": "When set to 'true', the connector will not attempt to flush the LGWR buffer to disk, allowing connecting to read-only databases.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": false + }, { "name": "camel.component.debezium-oracle.log-mining-readonly-hostname", "type": "java.lang.String", - "description": "The hostname the connector will use to connect and perform read-only operations for the the replica.", + "description": "The secondary Oracle instance where changes will be streamed", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration" }, { @@ -502,20 +544,6 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": false }, - { - "name": "camel.component.debezium-oracle.log-mining-scn-gap-detection-gap-size-min", - "type": "java.lang.Long", - "description": "Used for SCN gap detection, if the difference between current SCN and previous end SCN is bigger than this value, and the time difference of current SCN and previous end SCN is smaller than log.mining.scn.gap.detection.time.interval.max.ms, consider it a SCN gap.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 1000000 - }, - { - "name": "camel.component.debezium-oracle.log-mining-scn-gap-detection-time-interval-max-ms", - "type": "java.lang.Long", - "description": "Used for SCN gap detection, if the difference between current SCN and previous end SCN is bigger than log.mining.scn.gap.detection.gap.size.min, and the time difference of current SCN and previous end SCN is smaller than this value, consider it a SCN gap. The option is a long type.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 20000 - }, { "name": "camel.component.debezium-oracle.log-mining-session-max-ms", "type": "java.lang.Long", @@ -523,38 +551,10 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": 0 }, - { - "name": "camel.component.debezium-oracle.log-mining-sleep-time-default-ms", - "type": "java.lang.Long", - "description": "The amount of time that the connector will sleep after reading data from redo\/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 1000 - }, - { - "name": "camel.component.debezium-oracle.log-mining-sleep-time-increment-ms", - "type": "java.lang.Long", - "description": "The maximum amount of time that the connector will use to tune the optimal sleep time when reading data from LogMiner. Value is in milliseconds. The option is a long type.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 200 - }, - { - "name": "camel.component.debezium-oracle.log-mining-sleep-time-max-ms", - "type": "java.lang.Long", - "description": "The maximum amount of time that the connector will sleep after reading data from redo\/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 3000 - }, - { - "name": "camel.component.debezium-oracle.log-mining-sleep-time-min-ms", - "type": "java.lang.Long", - "description": "The minimum amount of time that the connector will sleep after reading data from redo\/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type.", - "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", - "defaultValue": 0 - }, { "name": "camel.component.debezium-oracle.log-mining-strategy", "type": "java.lang.String", - "description": "There are strategies: Online catalog with faster mining but no captured DDL. Another - with data dictionary loaded into REDO LOG files", + "description": "Defines the mining strategy and LogMiner session characteristics: 'redo_log_catalog' writes the data dictionary to the redo logs, is deprecated and will be removed in 3.7, 'online_catalog' uses the existing data dictionary and operates faster than 'redo_log_catalog' but requires schema changes in lock-step, 'hybrid' uses the existing data dictionary, operates faster than 'redo_log_catalog', and supports interleaved schema changes.", "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": "online_catalog" }, @@ -605,6 +605,20 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": 0 }, + { + "name": "camel.component.debezium-oracle.memory-management-schemas-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, + { + "name": "camel.component.debezium-oracle.memory-management-tables-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, { "name": "camel.component.debezium-oracle.message-key-columns", "type": "java.lang.String", @@ -818,6 +832,31 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": "none" }, + { + "name": "camel.component.debezium-oracle.secondary-dbname", + "type": "java.lang.String", + "description": "The secondary Oracle instance database name, if different from primary", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration" + }, + { + "name": "camel.component.debezium-oracle.secondary-hostname", + "type": "java.lang.String", + "description": "The secondary Oracle instance where changes will be streamed", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration" + }, + { + "name": "camel.component.debezium-oracle.secondary-port", + "type": "java.lang.Integer", + "description": "The secondary Oracle instance port where changes will be streamed", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": 1528 + }, + { + "name": "camel.component.debezium-oracle.secondary-url", + "type": "java.lang.String", + "description": "The secondary Oracle instance connection string URL where changes will be streamed", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration" + }, { "name": "camel.component.debezium-oracle.signal-data-collection", "type": "java.lang.String", @@ -967,6 +1006,13 @@ "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": "io.debezium.connector.oracle.OracleSourceInfoStructMaker" }, + { + "name": "camel.component.debezium-oracle.statistics-metrics-enabled", + "type": "java.lang.Boolean", + "description": "Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled.", + "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", + "defaultValue": true + }, { "name": "camel.component.debezium-oracle.streaming-delay-ms", "type": "java.lang.Long", @@ -989,7 +1035,7 @@ { "name": "camel.component.debezium-oracle.time-precision-mode", "type": "java.lang.String", - "description": "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 millisec [...] + "description": "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 millisec [...] "sourceType": "org.apache.camel.component.debezium.oracle.springboot.DebeziumOracleComponentConfiguration", "defaultValue": "adaptive" }, diff --git a/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres.json b/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres.json index 2b1c05ea907..fd33ffd3e7b 100644 --- a/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres.json +++ b/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres.json @@ -361,6 +361,20 @@ "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", "defaultValue": 0 }, + { + "name": "camel.component.debezium-postgres.memory-management-schemas-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, + { + "name": "camel.component.debezium-postgres.memory-management-tables-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, { "name": "camel.component.debezium-postgres.message-key-columns", "type": "java.lang.String", @@ -796,6 +810,13 @@ "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", "defaultValue": "io.debezium.connector.postgresql.PostgresSourceInfoStructMaker" }, + { + "name": "camel.component.debezium-postgres.statistics-metrics-enabled", + "type": "java.lang.Boolean", + "description": "Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled.", + "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", + "defaultValue": true + }, { "name": "camel.component.debezium-postgres.status-update-interval-ms", "type": "java.lang.Integer", @@ -832,7 +853,7 @@ { "name": "camel.component.debezium-postgres.time-precision-mode", "type": "java.lang.String", - "description": "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 millisec [...] + "description": "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 millisec [...] "sourceType": "org.apache.camel.component.debezium.postgres.springboot.DebeziumPostgresComponentConfiguration", "defaultValue": "adaptive" }, diff --git a/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver.json b/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver.json index 74bb3c817c5..6ada373d830 100644 --- a/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver.json +++ b/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver.json @@ -311,6 +311,20 @@ "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", "defaultValue": 0 }, + { + "name": "camel.component.debezium-sqlserver.memory-management-schemas-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, + { + "name": "camel.component.debezium-sqlserver.memory-management-tables-class", + "type": "java.lang.String", + "description": "The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.", + "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", + "defaultValue": "io.debezium.relational.ConcurrentMapTableMappingStorage" + }, { "name": "camel.component.debezium-sqlserver.message-key-columns", "type": "java.lang.String", @@ -635,6 +649,13 @@ "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", "defaultValue": "io.debezium.connector.sqlserver.SqlServerSourceInfoStructMaker" }, + { + "name": "camel.component.debezium-sqlserver.statistics-metrics-enabled", + "type": "java.lang.Boolean", + "description": "Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled.", + "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", + "defaultValue": true + }, { "name": "camel.component.debezium-sqlserver.streaming-delay-ms", "type": "java.lang.Long", @@ -671,7 +692,7 @@ { "name": "camel.component.debezium-sqlserver.time-precision-mode", "type": "java.lang.String", - "description": "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 millisec [...] + "description": "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 millisec [...] "sourceType": "org.apache.camel.component.debezium.sqlserver.springboot.DebeziumSqlserverComponentConfiguration", "defaultValue": "adaptive" }, diff --git a/docs/spring-boot/modules/ROOT/pages/starters/debezium-oracle.adoc b/docs/spring-boot/modules/ROOT/pages/starters/debezium-oracle.adoc index 07297a02705..864dfd577c2 100644 --- a/docs/spring-boot/modules/ROOT/pages/starters/debezium-oracle.adoc +++ b/docs/spring-boot/modules/ROOT/pages/starters/debezium-oracle.adoc @@ -23,7 +23,7 @@ Please refer to the above links for usage and configuration details. == Spring Boot Auto-Configuration -The starter supports 154 options, which are listed below. +The starter supports 161 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== @@ -34,6 +34,7 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean | camel.component.debezium-oracle.binary-handling-mode | Specify how binary (blob, binary, etc.) columns should be represented in change events, including: 'bytes' represents binary data as byte array (default); 'base64' represents binary data as base64-encoded string; 'base64-url-safe' represents binary data as base64-url-safe-encoded string; 'hex' represents binary data as hex-encoded (base16) string | bytes | String | camel.component.debezium-oracle.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, an [...] +| camel.component.debezium-oracle.capture-mode | Specifies the capture mode used to capture streaming changes from Oracle'primary' (the default) captures changes from the primary, specified by database. configurations, 'physical_standby' captures changes from a read-only physical standby, specified by secondary. configurations. | primary | String | camel.component.debezium-oracle.column-exclude-list | Regular expressions matching columns to exclude from change events | | String | camel.component.debezium-oracle.column-include-list | Regular expressions matching columns to include in change events | | String | camel.component.debezium-oracle.column-propagate-source-type | A comma-separated list of regular expressions matching fully-qualified names of columns that adds the columns original type and original length as parameters to the corresponding field schemas in the emitted change records. | | String @@ -74,10 +75,8 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.lob-enabled | When set to 'false', the default, LOB fields will not be captured nor emitted. When set to 'true', the connector will capture LOB fields and emit changes for those fields like any other column type. | false | Boolean | camel.component.debezium-oracle.log-mining-archive-log-only-mode | When set to 'false', the default, the connector will mine both archive log and redo logs to emit change events. When set to 'true', the connector will only mine archive logs. There are circumstances where its advantageous to only mine archive logs and accept latency in event emission due to frequent revolving redo logs. | false | Boolean | camel.component.debezium-oracle.log-mining-archive-log-only-scn-poll-interval-ms | The interval in milliseconds to wait between polls checking to see if the SCN is in the archive logs. The option is a long type. | 10000 | Long -| camel.component.debezium-oracle.log-mining-batch-size-default | The starting SCN interval size that the connector will use for reading data from redo/archive logs. | 20000 | Long -| camel.component.debezium-oracle.log-mining-batch-size-increment | Active batch size will be also increased/decreased by this amount for tuning connector throughput when needed. | 20000 | Long -| camel.component.debezium-oracle.log-mining-batch-size-max | The maximum SCN interval size that this connector will use when reading from redo/archive logs. | 100000 | Long -| camel.component.debezium-oracle.log-mining-batch-size-min | The minimum SCN interval size that this connector will try to read from redo/archive logs. | 1000 | Long +| camel.component.debezium-oracle.log-mining-buffer-deferred-transaction-retention-ms | Duration in milliseconds to retain deferred transaction metadata for transactions that never emit a DML event. By default, deferred transaction metadata is retained for 24 hours. This is independent of log.mining.transaction.retention.ms which governs cached transactions with events. The option is a long type. | 86400000 | Long +| camel.component.debezium-oracle.log-mining-buffer-deferred-transaction-start | Controls whether transaction start events are deferred when using buffered LogMiner. When enabled, transaction start events are stored in a lightweight metadata map. Transactions are only promoted to the transaction cache when a DML event is observed. The mining window is not pinned by transactions, allowing a block-by-block sliding window. | false | Boolean | camel.component.debezium-oracle.log-mining-buffer-drop-on-stop | When set to true the underlying buffer cache is not retained when the connector is stopped. When set to false (the default), the buffer cache is retained across restarts. | false | Boolean | camel.component.debezium-oracle.log-mining-buffer-ehcache-events-config | Specifies the inner body the Ehcache tag for the events cache, but should not include the nor the attributes as these are managed by Debezium. | | String | camel.component.debezium-oracle.log-mining-buffer-ehcache-global-config | Specifies any Ehcache global configurations such as services or persistence. This cannot include nor tags as these are managed by Debezium. | | String @@ -91,25 +90,26 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.log-mining-buffer-infinispan-cache-rollbacks | Specifies the XML configuration for the Infinispan 'rollbacks' cache | | String | camel.component.debezium-oracle.log-mining-buffer-infinispan-cache-schema-changes | Specifies the XML configuration for the Infinispan 'schema-changes' cache | | String | camel.component.debezium-oracle.log-mining-buffer-infinispan-cache-transactions | Specifies the XML configuration for the Infinispan 'transactions' cache | | String -| camel.component.debezium-oracle.log-mining-buffer-track-rs-id | This controls whether the 'RS_ID' column values are tracked. When set to true (the default), the 'RS_ID' values are buffered and provided in events when available. When set to false, the 'RS_ID' values are not buffered and can reduce the memory footprint. | true | Boolean +| camel.component.debezium-oracle.log-mining-buffer-memory-legacy-transaction-start | Controls whether transaction start events are deferred when using buffered LogMiner. When enabled, transaction start events are stored in a lightweight metadata map. Transactions are only promoted to the transaction cache when a DML event is observed. The mining window is not pinned by transactions, allowing a block-by-block sliding window. | false | Boolean +| camel.component.debezium-oracle.log-mining-buffer-track-client-id | This controls whether the 'CLIENT_ID' column values are tracked. When set to true (the default), the 'CLIENT_ID' values are buffered and provided in events when available. When set to false, the 'CLIENT_ID' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth. | true | Boolean +| camel.component.debezium-oracle.log-mining-buffer-track-commit-timestamp | This controls whether the 'COMMIT_TIMESTAMP' column values are tracked. When set to true (the default), the 'COMMIT_TIMESTAMP' values are buffered and provided in events when available. When set to false, the 'COMMIT_TIMESTAMP' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth. | true | Boolean +| camel.component.debezium-oracle.log-mining-buffer-track-rs-id | This controls whether the 'RS_ID' column values are tracked. When set to true (the default), the 'RS_ID' values are buffered and provided in events when available. When set to false, the 'RS_ID' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth. | true | Boolean +| camel.component.debezium-oracle.log-mining-buffer-track-start-timestamp | This controls whether the 'START_TIMESTAMP' column values are tracked. When set to true (the default), the 'START_TIMESTAMP' values are buffered and provided in events when available. When set to false, the 'START_TIMESTAMP' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth. | true | Boolean +| camel.component.debezium-oracle.log-mining-buffer-track-username | This controls whether the 'USERNAME' column values are tracked. When set to true (the default), the 'USERNAME' values are buffered and provided in events when available. When set to false, the 'USERNAME' column is excluded from the LogMiner query and its values are not buffered, reducing both the memory footprint and query bandwidth. | true | Boolean | camel.component.debezium-oracle.log-mining-buffer-transaction-events-threshold | The number of events a transaction can include before the transaction is discarded. This is useful for managing buffer memory and/or space when dealing with very large transactions. Defaults to 0, meaning that no threshold is applied and transactions can have unlimited events. | 0 | Long | camel.component.debezium-oracle.log-mining-buffer-type | The buffer type controls how the connector manages buffering transaction data. memory - Uses the JVM process' heap to buffer all transaction data. infinispan_embedded - This option uses an embedded Infinispan cache to buffer transaction data and persist it to disk. infinispan_remote - This option uses a remote Infinispan cluster to buffer transaction data and persist it to disk. ehcache - Use ehcache in embedded mode to buffer tr [...] | camel.component.debezium-oracle.log-mining-clientid-exclude-list | Comma separated list of client ids to exclude from LogMiner query. | | String | camel.component.debezium-oracle.log-mining-clientid-include-list | Comma separated list of client ids to include from LogMiner query. | | String | camel.component.debezium-oracle.log-mining-flush-table-name | The name of the flush table used by the connector, defaults to LOG_MINING_FLUSH. | LOG_MINING_FLUSH | String | camel.component.debezium-oracle.log-mining-include-redo-sql | When enabled, the transaction log REDO SQL will be included in the source information block. | false | Boolean +| camel.component.debezium-oracle.log-mining-log-count-min | Specifies the minimum number of logs to mine per redo thread. Setting this to 0 disables the cap, and all available logs are mined in a single pass. | 2 | Integer | camel.component.debezium-oracle.log-mining-path-dictionary | This is required when using the connector against a read-only database replica. | | String | camel.component.debezium-oracle.log-mining-query-filter-mode | Specifies how the filter configuration is applied to the LogMiner database query. none - The query does not apply any schema or table filters, all filtering is at runtime by the connector. in - The query uses SQL in-clause expressions to specify the schema or table filters. regex - The query uses Oracle REGEXP_LIKE expressions to specify the schema or table filters. | none | String -| camel.component.debezium-oracle.log-mining-readonly-hostname | The hostname the connector will use to connect and perform read-only operations for the the replica. | | String +| camel.component.debezium-oracle.log-mining-read-only | When set to 'true', the connector will not attempt to flush the LGWR buffer to disk, allowing connecting to read-only databases. | false | Boolean +| camel.component.debezium-oracle.log-mining-readonly-hostname | The secondary Oracle instance where changes will be streamed | | String | camel.component.debezium-oracle.log-mining-restart-connection | Debezium opens a database connection and keeps that connection open throughout the entire streaming phase. In some situations, this can lead to excessive SGA memory usage. By setting this option to 'true' (the default is 'false'), the connector will close and re-open a database connection after every detected log switch or if the log.mining.session.max.ms has been reached. | false | Boolean -| camel.component.debezium-oracle.log-mining-scn-gap-detection-gap-size-min | Used for SCN gap detection, if the difference between current SCN and previous end SCN is bigger than this value, and the time difference of current SCN and previous end SCN is smaller than log.mining.scn.gap.detection.time.interval.max.ms, consider it a SCN gap. | 1000000 | Long -| camel.component.debezium-oracle.log-mining-scn-gap-detection-time-interval-max-ms | Used for SCN gap detection, if the difference between current SCN and previous end SCN is bigger than log.mining.scn.gap.detection.gap.size.min, and the time difference of current SCN and previous end SCN is smaller than this value, consider it a SCN gap. The option is a long type. | 20000 | Long | camel.component.debezium-oracle.log-mining-session-max-ms | The maximum number of milliseconds that a LogMiner session lives for before being restarted. Defaults to 0 (indefinite until a log switch occurs). The option is a long type. | 0 | Long -| camel.component.debezium-oracle.log-mining-sleep-time-default-ms | The amount of time that the connector will sleep after reading data from redo/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type. | 1000 | Long -| camel.component.debezium-oracle.log-mining-sleep-time-increment-ms | The maximum amount of time that the connector will use to tune the optimal sleep time when reading data from LogMiner. Value is in milliseconds. The option is a long type. | 200 | Long -| camel.component.debezium-oracle.log-mining-sleep-time-max-ms | The maximum amount of time that the connector will sleep after reading data from redo/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type. | 3000 | Long -| camel.component.debezium-oracle.log-mining-sleep-time-min-ms | The minimum amount of time that the connector will sleep after reading data from redo/archive logs and before starting reading data again. Value is in milliseconds. The option is a long type. | 0 | Long -| camel.component.debezium-oracle.log-mining-strategy | There are strategies: Online catalog with faster mining but no captured DDL. Another - with data dictionary loaded into REDO LOG files | online_catalog | String +| camel.component.debezium-oracle.log-mining-strategy | Defines the mining strategy and LogMiner session characteristics: 'redo_log_catalog' writes the data dictionary to the redo logs, is deprecated and will be removed in 3.7, 'online_catalog' uses the existing data dictionary and operates faster than 'redo_log_catalog' but requires schema changes in lock-step, 'hybrid' uses the existing data dictionary, operates faster than 'redo_log_catalog', and supports interleaved schema changes. | [...] | camel.component.debezium-oracle.log-mining-transaction-retention-ms | Duration in milliseconds to keep long running transactions in transaction buffer between log mining sessions. By default, all transactions are retained. The option is a long type. | 0 | Long | camel.component.debezium-oracle.log-mining-username-exclude-list | Comma separated list of usernames to exclude from LogMiner query. | | String | camel.component.debezium-oracle.log-mining-username-include-list | Comma separated list of usernames to include from LogMiner query. | | String @@ -117,6 +117,8 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.max-batch-size | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer | camel.component.debezium-oracle.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-oracle.max-queue-size-in-bytes | Maximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded. Defaults to 0. Mean the feature is not enabled | 0 | Long +| camel.component.debezium-oracle.memory-management-schemas-class | The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String +| camel.component.debezium-oracle.memory-management-tables-class | The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String | camel.component.debezium-oracle.message-key-columns | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':', where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector, and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the tab [...] | camel.component.debezium-oracle.notification-enabled-channels | List of notification channels names that are enabled. | | String | camel.component.debezium-oracle.notification-sink-topic-name | The name of the topic for the notifications. This is required in case 'sink' is in the list of enabled channels | | String @@ -150,6 +152,10 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.schema-history-internal-store-only-captured-databases-ddl | Controls what DDL will Debezium store in database schema history. By default (false) Debezium will store all incoming DDL statements. If set to true, then only DDL that manipulates a table from captured schema/database will be stored. | false | Boolean | camel.component.debezium-oracle.schema-history-internal-store-only-captured-tables-ddl | Controls what DDL will Debezium store in database schema history. By default (false) Debezium will store all incoming DDL statements. If set to true, then only DDL that manipulates a captured table will be stored. | false | Boolean | camel.component.debezium-oracle.schema-name-adjustment-mode | Specify how schema names should be adjusted for compatibility with the message converter used by the connector, including: 'avro' replaces the characters that cannot be used in the Avro type name with underscore; 'avro_unicode' replaces the underscore or characters that cannot be used in the Avro type name with corresponding unicode like _uxxxx. Note: _ is an escape sequence like backslash in Java;'none' does not apply any a [...] +| camel.component.debezium-oracle.secondary-dbname | The secondary Oracle instance database name, if different from primary | | String +| camel.component.debezium-oracle.secondary-hostname | The secondary Oracle instance where changes will be streamed | | String +| camel.component.debezium-oracle.secondary-port | The secondary Oracle instance port where changes will be streamed | 1528 | Integer +| camel.component.debezium-oracle.secondary-url | The secondary Oracle instance connection string URL where changes will be streamed | | String | camel.component.debezium-oracle.signal-data-collection | The name of the data collection that is used to send signals/commands to Debezium. For multi-partition mode connectors, multiple signal data collections can be specified as a comma-separated list. Signaling is disabled when not set. | | String | camel.component.debezium-oracle.signal-enabled-channels | List of channels names that are enabled. Source channel is enabled by default | source | String | camel.component.debezium-oracle.signal-poll-interval-ms | Interval for looking for new signals in registered channels, given in milliseconds. Defaults to 5 seconds. The option is a long type. | 5000 | Long @@ -172,10 +178,11 @@ The starter supports 154 options, which are listed below. | camel.component.debezium-oracle.snapshot-select-statement-overrides | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connectors. 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' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', re [...] | camel.component.debezium-oracle.snapshot-tables-order-by-row-count | Controls the order in which tables are processed in the initial snapshot. A descending value will order the tables by row count descending. A ascending value will order the tables by row count ascending. A value of disabled (the default) will disable ordering by row count. | disabled | String | camel.component.debezium-oracle.sourceinfo-struct-maker | The name of the SourceInfoStructMaker class that returns SourceInfo schema and struct. | io.debezium.connector.oracle.OracleSourceInfoStructMaker | String +| camel.component.debezium-oracle.statistics-metrics-enabled | Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled. | true | Boolean | camel.component.debezium-oracle.streaming-delay-ms | A delay period after the snapshot is completed and the streaming begins, given in milliseconds. Defaults to 0 ms. The option is a long type. | 0 | Long | camel.component.debezium-oracle.table-exclude-list | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String | camel.component.debezium-oracle.table-include-list | The tables for which changes are to be captured | | String -| camel.component.debezium-oracle.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 for Time, Date, [...] +| camel.component.debezium-oracle.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 for Time, Date, [...] | camel.component.debezium-oracle.tombstones-on-delete | Whether delete operations should be represented by a delete event and a subsequent tombstone 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-oracle.topic-naming-strategy | The name of the TopicNamingStrategy class that should be used to determine the topic name for data change, schema change, transaction, heartbeat event etc. | io.debezium.schema.SchemaTopicNamingStrategy | String | camel.component.debezium-oracle.topic-prefix | Topic prefix that identifies and provides a namespace for the particular database server/cluster is capturing changes. The topic prefix should be unique across all other connectors, since it is used as a prefix for all Kafka topic names that receive events emitted by this connector. Only alphanumeric characters, hyphens, dots and underscores must be accepted. | | String diff --git a/docs/spring-boot/modules/ROOT/pages/starters/debezium-postgres.adoc b/docs/spring-boot/modules/ROOT/pages/starters/debezium-postgres.adoc index 8a7b080cb76..5cfac812f20 100644 --- a/docs/spring-boot/modules/ROOT/pages/starters/debezium-postgres.adoc +++ b/docs/spring-boot/modules/ROOT/pages/starters/debezium-postgres.adoc @@ -23,7 +23,7 @@ Please refer to the above links for usage and configuration details. == Spring Boot Auto-Configuration -The starter supports 130 options, which are listed below. +The starter supports 133 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== @@ -80,6 +80,8 @@ The starter supports 130 options, which are listed below. | camel.component.debezium-postgres.max-batch-size | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer | camel.component.debezium-postgres.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.max-queue-size-in-bytes | Maximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded. Defaults to 0. Mean the feature is not enabled | 0 | Long +| camel.component.debezium-postgres.memory-management-schemas-class | The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String +| camel.component.debezium-postgres.memory-management-tables-class | The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String | camel.component.debezium-postgres.message-key-columns | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':', where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector, and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the t [...] | camel.component.debezium-postgres.message-prefix-exclude-list | A comma-separated list of regular expressions that match the logical decoding message prefixes to be excluded from monitoring. | | String | camel.component.debezium-postgres.message-prefix-include-list | A comma-separated list of regular expressions that match the logical decoding message prefixes to be monitored. All prefixes are monitored by default. | | String @@ -146,12 +148,13 @@ The starter supports 130 options, which are listed below. | camel.component.debezium-postgres.snapshot-select-statement-overrides | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connectors. 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' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', [...] | camel.component.debezium-postgres.snapshot-tables-order-by-row-count | Controls the order in which tables are processed in the initial snapshot. A descending value will order the tables by row count descending. A ascending value will order the tables by row count ascending. A value of disabled (the default) will disable ordering by row count. | disabled | String | camel.component.debezium-postgres.sourceinfo-struct-maker | The name of the SourceInfoStructMaker class that returns SourceInfo schema and struct. | io.debezium.connector.postgresql.PostgresSourceInfoStructMaker | String +| camel.component.debezium-postgres.statistics-metrics-enabled | Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled. | true | Boolean | camel.component.debezium-postgres.status-update-interval-ms | Frequency for sending replication connection status updates to the server, given in milliseconds. Defaults to 10 seconds (10,000 ms). The option is a int type. | 10000 | Integer | camel.component.debezium-postgres.streaming-delay-ms | A delay period after the snapshot is completed and the streaming begins, given in milliseconds. Defaults to 0 ms. The option is a long type. | 0 | Long | camel.component.debezium-postgres.table-exclude-list | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String | camel.component.debezium-postgres.table-ignore-builtin | Flag specifying whether built-in tables should be ignored. | true | Boolean | camel.component.debezium-postgres.table-include-list | The tables for which changes are to be captured | | String -| camel.component.debezium-postgres.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 for Time, Date [...] +| camel.component.debezium-postgres.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 for Time, Date [...] | camel.component.debezium-postgres.tombstones-on-delete | Whether delete operations should be represented by a delete event and a subsequent tombstone 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.topic-naming-strategy | The name of the TopicNamingStrategy class that should be used to determine the topic name for data change, schema change, transaction, heartbeat event etc. | io.debezium.schema.SchemaTopicNamingStrategy | String | camel.component.debezium-postgres.topic-prefix | Topic prefix that identifies and provides a namespace for the particular database server/cluster is capturing changes. The topic prefix should be unique across all other connectors, since it is used as a prefix for all Kafka topic names that receive events emitted by this connector. Only alphanumeric characters, hyphens, dots and underscores must be accepted. | | String diff --git a/docs/spring-boot/modules/ROOT/pages/starters/debezium-sqlserver.adoc b/docs/spring-boot/modules/ROOT/pages/starters/debezium-sqlserver.adoc index 6b40d179ab0..5dd559de29d 100644 --- a/docs/spring-boot/modules/ROOT/pages/starters/debezium-sqlserver.adoc +++ b/docs/spring-boot/modules/ROOT/pages/starters/debezium-sqlserver.adoc @@ -23,7 +23,7 @@ Please refer to the above links for usage and configuration details. == Spring Boot Auto-Configuration -The starter supports 103 options, which are listed below. +The starter supports 106 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== @@ -72,6 +72,8 @@ The starter supports 103 options, which are listed below. | camel.component.debezium-sqlserver.max-iteration-transactions | This property can be used to reduce the connector memory usage footprint when changes are streamed from multiple tables per database. | 500 | Integer | camel.component.debezium-sqlserver.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-sqlserver.max-queue-size-in-bytes | Maximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded. Defaults to 0. Mean the feature is not enabled | 0 | Long +| camel.component.debezium-sqlserver.memory-management-schemas-class | The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String +| camel.component.debezium-sqlserver.memory-management-tables-class | The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage. | io.debezium.relational.ConcurrentMapTableMappingStorage | String | camel.component.debezium-sqlserver.message-key-columns | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':', where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector, and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the [...] | camel.component.debezium-sqlserver.notification-enabled-channels | List of notification channels names that are enabled. | | String | camel.component.debezium-sqlserver.notification-sink-topic-name | The name of the topic for the notifications. This is required in case 'sink' is in the list of enabled channels | | String @@ -121,12 +123,13 @@ The starter supports 103 options, which are listed below. | camel.component.debezium-sqlserver.snapshot-select-statement-overrides | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connectors. 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' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', [...] | camel.component.debezium-sqlserver.snapshot-tables-order-by-row-count | Controls the order in which tables are processed in the initial snapshot. A descending value will order the tables by row count descending. A ascending value will order the tables by row count ascending. A value of disabled (the default) will disable ordering by row count. | disabled | String | camel.component.debezium-sqlserver.sourceinfo-struct-maker | The name of the SourceInfoStructMaker class that returns SourceInfo schema and struct. | io.debezium.connector.sqlserver.SqlServerSourceInfoStructMaker | String +| camel.component.debezium-sqlserver.statistics-metrics-enabled | Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled. | true | Boolean | camel.component.debezium-sqlserver.streaming-delay-ms | A delay period after the snapshot is completed and the streaming begins, given in milliseconds. Defaults to 0 ms. The option is a long type. | 0 | Long | camel.component.debezium-sqlserver.streaming-fetch-size | Specifies the maximum number of rows that should be read in one go from each table while streaming. The connector will read the table contents in multiple batches of this size. Defaults to 0 which means no limit. | 0 | Integer | camel.component.debezium-sqlserver.table-exclude-list | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String | camel.component.debezium-sqlserver.table-ignore-builtin | Flag specifying whether built-in tables should be ignored. | true | Boolean | camel.component.debezium-sqlserver.table-include-list | The tables for which changes are to be captured | | String -| camel.component.debezium-sqlserver.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 for Time, Dat [...] +| camel.component.debezium-sqlserver.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 for Time, Dat [...] | camel.component.debezium-sqlserver.tombstones-on-delete | Whether delete operations should be represented by a delete event and a subsequent tombstone 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-sqlserver.topic-naming-strategy | The name of the TopicNamingStrategy class that should be used to determine the topic name for data change, schema change, transaction, heartbeat event etc. | io.debezium.schema.SchemaTopicNamingStrategy | String | camel.component.debezium-sqlserver.topic-prefix | Topic prefix that identifies and provides a namespace for the particular database server/cluster is capturing changes. The topic prefix should be unique across all other connectors, since it is used as a prefix for all Kafka topic names that receive events emitted by this connector. Only alphanumeric characters, hyphens, dots and underscores must be accepted. | | String
