You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/06/15 18:12:09 UTC

[jira] [Created] (KAFKA-3845) Support per-connector converters

Ewen Cheslack-Postava created KAFKA-3845:
--------------------------------------------

             Summary: Support per-connector converters
                 Key: KAFKA-3845
                 URL: https://issues.apache.org/jira/browse/KAFKA-3845
             Project: Kafka
          Issue Type: Bug
          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)