Repository: kafka Updated Branches: refs/heads/trunk 3a244b783 -> ca3f3a492
MINOR: Document that Connect topics should use compaction Update documentation for Kafka Connect distributedâs config.storage.topic, offset.storage.topic, and status.storage.topic configuration values to indicate that all three should refer to compacted topics. Author: Mathieu Fenniak <mathieu.fenn...@replicon.com> Reviewers: Jason Gustafson Closes #1832 from mfenniak/kafka-connect-topic-docs Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/ca3f3a49 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/ca3f3a49 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/ca3f3a49 Branch: refs/heads/trunk Commit: ca3f3a492c1f10eda965c8402075a3e666f47885 Parents: 3a244b7 Author: Mathieu Fenniak <mathieu.fenn...@replicon.com> Authored: Wed Sep 7 17:34:24 2016 -0700 Committer: Jason Gustafson <ja...@confluent.io> Committed: Wed Sep 7 17:34:24 2016 -0700 ---------------------------------------------------------------------- docs/connect.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/ca3f3a49/docs/connect.html ---------------------------------------------------------------------- diff --git a/docs/connect.html b/docs/connect.html index de3b5aa..d8431a8 100644 --- a/docs/connect.html +++ b/docs/connect.html @@ -68,9 +68,9 @@ The difference is in the class which is started and the configuration parameters In particular, the following configuration parameters, in addition to the common settings mentioned above, are critical to set before starting your cluster: <ul> <li><code>group.id</code> (default <code>connect-cluster</code>) - unique name for the cluster, used in forming the Connect cluster group; note that this <b>must not conflict</b> with consumer group IDs</li> - <li><code>config.storage.topic</code> (default <code>connect-configs</code>) - 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.</li> - <li><code>offset.storage.topic</code> (default <code>connect-offsets</code>) - topic to use for storing offsets; this topic should have many partitions and be replicated</li> - <li><code>status.storage.topic</code> (default <code>connect-status</code>) - topic to use for storing statuses; this topic can have multiple partitions and should be replicated</li> + <li><code>config.storage.topic</code> (default <code>connect-configs</code>) - topic to use for storing connector and task configurations; note that this should be a single partition, highly replicated, compacted topic. You may need to manually create the topic to ensure the correct configuration as auto created topics may have multiple partitions or be automatically configured for deletion rather than compaction</li> + <li><code>offset.storage.topic</code> (default <code>connect-offsets</code>) - topic to use for storing offsets; this topic should have many partitions, be replicated, and be configured for compaction</li> + <li><code>status.storage.topic</code> (default <code>connect-status</code>) - topic to use for storing statuses; this topic can have multiple partitions, and should be replicated and configured for compaction</li> </ul> Note that in distributed mode the connector configurations are not passed on the command line. Instead, use the REST API described below to create, modify, and destroy connectors.
