[
https://issues.apache.org/jira/browse/KAFKA-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-3845:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 1721
[https://github.com/apache/kafka/pull/1721]
> 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)
