[
https://issues.apache.org/jira/browse/KAFKA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007911#comment-15007911
]
ASF GitHub Bot commented on KAFKA-2848:
---------------------------------------
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/539
KAFKA-2848: Use client SSL/SASL config utilities in Kafka Connect to avoid
duplication of configs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka
kafka-2848-reuse-ssl-sasl-client-configs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/539.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 #539
----
commit 752d208cb3b607150cd016cc2776008dda0984b8
Author: Ewen Cheslack-Postava <m...@ewencp.org>
Date: 2015-11-17T02:45:53Z
KAFKA-2848: Use client SSL/SASL config utilities in Kafka Connect to avoid
duplication of configs.
----
> Use withClientSslSupport/withClientSaslSupport in Kafka Connect
> ---------------------------------------------------------------
>
> Key: KAFKA-2848
> URL: https://issues.apache.org/jira/browse/KAFKA-2848
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Fix For: 0.9.1.0
>
>
> These were introduced in KAFKA-2687 and applied to the ProducerConfig and
> ConsumerConfig classes, but did not get applied to Kafka Connect configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
