[ 
https://issues.apache.org/jira/browse/KAFKA-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418352#comment-15418352
 ] 

ASF GitHub Bot commented on KAFKA-3845:
---------------------------------------

GitHub user ewencp opened a pull request:

    https://github.com/apache/kafka/pull/1721

    KAFKA-3845: KIP-75: Add per-connector converters

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ewencp/kafka 
kafka-3845-per-connector-converters

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1721.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 #1721
    
----
commit d7763f995ed84df1af41bf99f96340a17ef051c5
Author: Ewen Cheslack-Postava <m...@ewencp.org>
Date:   2016-08-12T03:32:57Z

    KAFKA-3845: KIP-75: Add per-connector converters

----


> Support per-connector converters
> --------------------------------
>
>                 Key: KAFKA-3845
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3845
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.0
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Ewen Cheslack-Postava
>            Priority: Critical
>             Fix For: 0.10.1.0
>
>
> While good for default configuration and reducing the total configuration the 
> user needs to do, it's inconvenient requiring that all connectors on a 
> cluster need to use the same converter. It's definitely a good idea to stay 
> consistent, but occasionally you may need a special converters, e.g. one 
> source of data happens to come in JSON despite you standardizing on Avro.
> Note that these configs are connector-level in the sense that the entire 
> connector should use a single converter type, but since converters are used 
> by tasks the config needs to be automatically propagated to tasks.
> This is effectively public API change as it is adding a built-in config for 
> connectors/tasks, so this probably requires a KIP.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to