DBZ-7616 Document database.query.timeout.ms property
Co-authored-by: roldanbob <broldan@redhat.com>
This commit is contained in:
parent
7ab02735bf
commit
4310a6fda6
@ -3045,8 +3045,9 @@ User intervention is required to restart the connector.
|
||||
After the next failure, the connector stops, and user intervention is required to restart it.
|
||||
|
||||
|[[db2-property-database-query-timeout-ms]]<<db2-property-database-query-timeout-ms, `database.query.timeout.ms`>>
|
||||
|`600000`
|
||||
|Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit.
|
||||
|`600000` (10 minutes)
|
||||
|Specifies the time, in milliseconds, that the connector waits for a query to complete.
|
||||
Set the value to `0` (zero) to remove the timeout limit.
|
||||
|
||||
|===
|
||||
|
||||
|
@ -2649,8 +2649,9 @@ You can define tags to identify particular application instances, environments,
|
||||
|The maximum number of retries on retriable errors (e.g. connection errors) before failing (-1 = no limit, 0 = disabled, > 0 = num of retries).
|
||||
|
||||
|[[informix-property-database-query-timeout-ms]]<<informix-property-database-query-timeout-ms, `database.query.timeout.ms`>>
|
||||
|`600000`
|
||||
|Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit.
|
||||
|`600000` (10 minutes)
|
||||
|Specifies the time, in milliseconds, that the connector waits for a query to complete.
|
||||
Set the value to `0` (zero) to remove the timeout limit.
|
||||
|
||||
|===
|
||||
|
||||
|
@ -3922,8 +3922,9 @@ Set one of the following options:
|
||||
`skip`:: The connector writes a `null` value to the event field for the column that failed conversion, and writes a message to the debug log.
|
||||
|
||||
|[[mysql-property-database-query-timeout-ms]]<<mysql-property-database-query-timeout-ms, `database.query.timeout.ms`>>
|
||||
|`600000`
|
||||
|Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit.
|
||||
|`600000` (10 minutes)
|
||||
|Specifies the time, in milliseconds, that the connector waits for a query to complete.
|
||||
Set the value to `0` (zero) to remove the timeout limit.
|
||||
|===
|
||||
|
||||
[id="debezium-mysql-connector-database-history-configuration-properties"]
|
||||
|
@ -3697,8 +3697,9 @@ User intervention is required to restart the connector.
|
||||
After the next failure, the connector stops, and user intervention is required to restart it.
|
||||
|
||||
|[[postgresql-property-database-query-timeout-ms]]<<postgresql-property-database-query-timeout-ms, `database.query.timeout.ms`>>
|
||||
|`600000`
|
||||
|Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit.
|
||||
|`600000` (10 minutes)
|
||||
|Specifies the time, in milliseconds, that the connector waits for a query to complete.
|
||||
Set the value to `0` (zero) to remove the timeout limit.
|
||||
|===
|
||||
|
||||
[id="postgresql-pass-through-properties"]
|
||||
|
@ -3270,8 +3270,9 @@ After the next failure, the connector stops, and user intervention is required t
|
||||
* `direct`: Makes the connector to query change tables directly. Switching to `direct` mode and creating an index on `(\\__$start_lsn ASC, __$seqval ASC, __$operation ASC)` columns for each change table significantly speeds up querying CDC data.
|
||||
|
||||
|[[sqlserver-property-database-query-timeout-ms]]<<sqlserver-property-database-query-timeout-ms, `database.query.timeout.ms`>>
|
||||
|`600000`
|
||||
|Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit.
|
||||
|`600000` (10 minutes)
|
||||
|Specifies the time, in milliseconds, that the connector waits for a query to complete.
|
||||
Set the value to `0` (zero) to remove the timeout limit.
|
||||
|===
|
||||
|
||||
[id="debezium-sqlserver-connector-database-history-configuration-properties"]
|
||||
|
Loading…
Reference in New Issue
Block a user