alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-1995 returned content about pass-through properties for MySQL connector

Browse Source
This commit is contained in:
Tova Cohen 2020-06-16 17:41:25 -04:00 committed by Jiri Pechanec
parent db2fb28be3
commit 90c3b29b8b
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
documentation/modules/ROOT/partials/modules/cdc-mysql-connector/r_mysql-connector-configuration-properties.adoc
View File

@ -6,7 +6,7 @@
The configuration properties listed here are *required* to run the {prodname} MySQL connector. There are also <<advanced-mysql-connector-properties, advanced MySQL connector properties>> whose default value rarely needs to be changed and therefore, they do not need to be specified in the connector configuration.
TIP: The {prodname} MySQL connector supports _pass-through_ configuration when creating the Kafka producer and consumer. See link:{link-kafka-docs}.html[the Kafka documentation] for more details on _pass-through_ properties.
TIP: The {prodname} MySQL connector supports _pass-through_ configuration when creating the Kafka producer and consumer. See information about pass-through properties at the end of this section, and also see link:{link-kafka-docs}.html[the Kafka documentation] for more details about _pass-through_ properties.
[cols="3,2,5"]
|===
@ -352,3 +352,24 @@ endif::community[]
The operations include: `c` for inserts, `u` for updates, and `d` for deletes.
By default, no operations are skipped.
|===
The MySQL connector also supports pass-through configuration properties that are used when creating the Kafka producer and consumer. Specifically, all connector configuration properties that begin with the `database.history.producer.` prefix are used (without the prefix) when creating the Kafka producer that writes to the database history. All properties that begin with the prefix `database.history.consumer.` are used (without the prefix) when creating the Kafka consumer that reads the database history upon connector start-up.
For example, the following connector configuration properties can be used to secure connections to the Kafka broker:
----
database.history.producer.security.protocol=SSL
database.history.producer.ssl.keystore.location=/var/private/ssl/kafka.server.keystore.jks
database.history.producer.ssl.keystore.password=test1234
database.history.producer.ssl.truststore.location=/var/private/ssl/kafka.server.truststore.jks
database.history.producer.ssl.truststore.password=test1234
database.history.producer.ssl.key.password=test1234
database.history.consumer.security.protocol=SSL
database.history.consumer.ssl.keystore.location=/var/private/ssl/kafka.server.keystore.jks
database.history.consumer.ssl.keystore.password=test1234
database.history.consumer.ssl.truststore.location=/var/private/ssl/kafka.server.truststore.jks
database.history.consumer.ssl.truststore.password=test1234
database.history.consumer.ssl.key.password=test1234
----
In addition to the pass-through properties for the Kafka producer and consumer, the properties starting with `database.`, for example, `database.tinyInt1isBit=false` are passed to the JDBC URL.