[
https://issues.apache.org/jira/browse/KAFKA-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389961#comment-15389961
]
ASF GitHub Bot commented on KAFKA-2932:
---------------------------------------
GitHub user cotedm opened a pull request:
https://github.com/apache/kafka/pull/1653
KAFKA-2932: Adjust importance level of Kafka Connect configs
@ewencp I went down the list of connect configs and it looks like only the
internal converter configs are mismarked. It looks like the `cluster` config
that is present in the current docs is already gone. The only other values I
can see arguing to change importance on are the ssl configs (marked high) but
they are consistent with the producer/consumer config docs so that's at least
consistent. Everything else marked high looks either mandatory or requires
consideration in a production deployment to me.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cotedm/kafka KAFKA-2932
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1653.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1653
----
commit c3e076a75e1e714c2585e9b976f5b746d804eaa5
Author: Dustin Cote <[email protected]>
Date: 2016-07-22T18:01:39Z
lower importance rating for internal converter settings
----
> Adjust importance level of Kafka Connect configs
> ------------------------------------------------
>
> Key: KAFKA-2932
> URL: https://issues.apache.org/jira/browse/KAFKA-2932
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.9.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Dustin Cote
>
> Some of the configuration importance levels are out of whack, probably due to
> the way they evolved over time. For example, the internal converter settings
> are currently marked with high importance, but they are really an internal
> implementation detail that the user usually shouldn't need to worry about.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
