Created
July 10, 2017 20:31
-
-
Save diegoicosta/561402a3cca6ce2253489c7a1fd9aeff to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# These are defaults. This file just demonstrates how to override some settings. | |
bootstrap.servers=localhost:9092 | |
# unique name for the cluster, used in forming the Connect cluster group. Note that this must not conflict with consumer group IDs | |
group.id=connect-cluster | |
# The converters specify the format of data in Kafka and how to translate it into Connect data. Every Connect user will | |
# need to configure these based on the format they want their data in when loaded from or stored into Kafka | |
key.converter=org.apache.kafka.connect.json.JsonConverter | |
value.converter=org.apache.kafka.connect.json.JsonConverter | |
# Converter-specific settings can be passed in by prefixing the Converter's setting with the converter we want to apply | |
# it to | |
key.converter.schemas.enable=true | |
value.converter.schemas.enable=true | |
# The internal converter used for offsets and config data is configurable and must be specified, but most users will | |
# always want to use the built-in default. Offset and config data is never visible outside of Kafka Connect in this format. | |
internal.key.converter=org.apache.kafka.connect.json.JsonConverter | |
internal.value.converter=org.apache.kafka.connect.json.JsonConverter | |
internal.key.converter.schemas.enable=false | |
internal.value.converter.schemas.enable=false | |
# Topic to use for storing offsets. This topic should have many partitions and be replicated. | |
offset.storage.topic=connect-offsets | |
# Topic to use for storing connector and task configurations; note that this should be a single partition, highly replicated topic. | |
# You may need to manually create the topic to ensure single partition for the config topic as auto created topics may have multiple partitions. | |
config.storage.topic=connect-configs | |
# Topic to use for storing statuses. This topic can have multiple partitions and should be replicated. | |
status.storage.topic=connect-status | |
# Flush much faster than normal, which is useful for testing/debugging | |
offset.flush.interval.ms=10000 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment