kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-5540) Deprecate and remove internal converter configs
Date Thu, 29 Jun 2017 21:14:02 GMT
Ewen Cheslack-Postava created KAFKA-5540:

             Summary: 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:
            Reporter: Ewen Cheslack-Postava

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

View raw message