-
Enhancement
-
Resolution: Unresolved
-
Minor
-
1.8.0.Final
-
None
-
False
-
-
False
When running Debezium Server standalone, without KConnect, the `application.properties` file is used to set properties.
When using Debezium with a Kafka sink and KafkaOffsetBackingStore to store offsets inside a Kafka topic, this done like this:
debezium.sink.type=kafka
debezium.sink.kafka.producer.key.serializer=org.apache.kafka.common.serialization.ByteArraySerializer
debezium.sink.kafka.producer.value.serializer=org.apache.kafka.common.serialization.ByteArraySerializer
debezium.sink.kafka.producer.bootstrap.servers=${var.kafka_bootstrap_servers}
debezium.sink.kafka.producer.security.protocol=SASL_SSL
debezium.sink.kafka.producer.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username='${var.kafka_secrets.api_key}' password='${var.kafka_secrets.api_secret}';
debezium.source.offset.storage=org.apache.kafka.connect.storage.KafkaOffsetBackingStore
debezium.source.offset.storage.topic=${var.offset_topic_name}
debezium.source.offset.storage.partitions=1
debezium.source.offset.storage.replication.factor=1
debezium.source.offset.flush.interval.ms=0
debezium.source.bootstrap.servers=${var.kafka_bootstrap_servers}
debezium.source.security.protocol=SASL_SSL
debezium.source.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username='${var.kafka_secrets.api_key}' password='${var.kafka_secrets.api_secret}';
debezium.source.sasl.mechanism=PLAIN
You can see that some properties are the same but under different path in the properties file and especially things like `bootstrap.servers` or security related properties should be reused on the producer side if possible.
