|
| 1 | +## |
| 2 | +# Licensed to the Apache Software Foundation (ASF) under one or more |
| 3 | +# contributor license agreements. See the NOTICE file distributed with |
| 4 | +# this work for additional information regarding copyright ownership. |
| 5 | +# The ASF licenses this file to You under the Apache License, Version 2.0 |
| 6 | +# (the "License"); you may not use this file except in compliance with |
| 7 | +# the License. You may obtain a copy of the License at |
| 8 | +# |
| 9 | +# http://www.apache.org/licenses/LICENSE-2.0 |
| 10 | +# |
| 11 | +# Unless required by applicable law or agreed to in writing, software |
| 12 | +# distributed under the License is distributed on an "AS IS" BASIS, |
| 13 | +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 14 | +# See the License for the specific language governing permissions and |
| 15 | +# limitations under the License. |
| 16 | +## |
| 17 | + |
| 18 | +# This file contains some of the configurations for the Kafka Connect distributed worker. This file is intended |
| 19 | +# to be used with the examples, and some settings may differ from those used in a production system, especially |
| 20 | +# the `bootstrap.servers` and those specifying replication factors. |
| 21 | + |
| 22 | +# A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. |
| 23 | +bootstrap.servers=<BOOTSTRAP_SERVERS> |
| 24 | +security.protocol=SASL_SSL |
| 25 | +sasl.mechanism=PLAIN |
| 26 | +sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="token" password="<APIKEY>"; |
| 27 | + |
| 28 | +consumer.security.protocol=SASL_SSL |
| 29 | +consumer.sasl.mechanism=PLAIN |
| 30 | +consumer.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="token" password="<APIKEY>"; |
| 31 | + |
| 32 | +producer.security.protocol=SASL_SSL |
| 33 | +producer.sasl.mechanism=PLAIN |
| 34 | +producer.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="token" password="<APIKEY>"; |
| 35 | + |
| 36 | +plugin.path=/opt/connectors |
| 37 | + |
| 38 | +# unique name for the cluster, used in forming the Connect cluster group. Note that this must not conflict with consumer group IDs |
| 39 | +group.id=connect-cluster |
| 40 | + |
| 41 | +# The converters specify the format of data in Kafka and how to translate it into Connect data. Every Connect user will |
| 42 | +# need to configure these based on the format they want their data in when loaded from or stored into Kafka |
| 43 | +key.converter=org.apache.kafka.connect.json.JsonConverter |
| 44 | +value.converter=org.apache.kafka.connect.json.JsonConverter |
| 45 | +# Converter-specific settings can be passed in by prefixing the Converter's setting with the converter we want to apply |
| 46 | +# it to |
| 47 | +key.converter.schemas.enable=true |
| 48 | +value.converter.schemas.enable=true |
| 49 | + |
| 50 | +# Topic to use for storing offsets. This topic should have many partitions and be replicated and compacted. |
| 51 | +# Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create |
| 52 | +# the topic before starting Kafka Connect if a specific topic configuration is needed. |
| 53 | +# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value. |
| 54 | +# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able |
| 55 | +# to run this example on a single-broker cluster and so here we instead set the replication factor to 1. |
| 56 | +offset.storage.topic=connect-offsets |
| 57 | +offset.storage.replication.factor=3 |
| 58 | +#offset.storage.partitions=25 |
| 59 | + |
| 60 | +# Topic to use for storing connector and task configurations; note that this should be a single partition, highly replicated, |
| 61 | +# and compacted topic. Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create |
| 62 | +# the topic before starting Kafka Connect if a specific topic configuration is needed. |
| 63 | +# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value. |
| 64 | +# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able |
| 65 | +# to run this example on a single-broker cluster and so here we instead set the replication factor to 1. |
| 66 | +config.storage.topic=connect-configs |
| 67 | +config.storage.replication.factor=3 |
| 68 | + |
| 69 | +# Topic to use for storing statuses. This topic can have multiple partitions and should be replicated and compacted. |
| 70 | +# Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create |
| 71 | +# the topic before starting Kafka Connect if a specific topic configuration is needed. |
| 72 | +# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value. |
| 73 | +# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able |
| 74 | +# to run this example on a single-broker cluster and so here we instead set the replication factor to 1. |
| 75 | +status.storage.topic=connect-status |
| 76 | +status.storage.replication.factor=3 |
| 77 | +#status.storage.partitions=5 |
| 78 | + |
| 79 | +# Flush much faster than normal, which is useful for testing/debugging |
| 80 | +offset.flush.interval.ms=10000 |
0 commit comments