[jira] [Commented] (KAFKA-5540) Deprecate and remove internal converter configs

["Umesh Chaudhary (JIRA)" <ji...@apache.org>]

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

Umesh Chaudhary commented on KAFKA-5540:
----------------------------------------

[~ewencp] I would like to work on this and will create the KIP as well. Let me know if I should proceed. 

> Deprecate and remove internal converter configs
> -----------------------------------------------
>
>                 Key: KAFKA-5540
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5540
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.11.0.0
>            Reporter: Ewen Cheslack-Postava
>              Labels: needs-kip
>
> The internal.key.converter and internal.value.converter were original exposed as configs because a) they are actually pluggable and b) providing a default would require relying on the JsonConverter always being available, which until we had classloader isolation it was possible might be removed for compatibility reasons.
> However, this has ultimately just caused a lot more trouble and confusion than it is worth. We should deprecate the configs, give them a default of JsonConverter (which is also kind of nice since it results in human-readable data in the internal topics), and then ultimately remove them in the next major version.
> These are all public APIs so this will need a small KIP before we can make the change.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)