You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Mitch Seymour (JIRA)" <ji...@apache.org> on 2017/03/11 03:28:04 UTC
[jira] [Assigned] (KAFKA-4882) Remove internal converter
configuration from example property files
[ https://issues.apache.org/jira/browse/KAFKA-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mitch Seymour reassigned KAFKA-4882:
------------------------------------
Assignee: Mitch Seymour
> Remove internal converter configuration from example property files
> -------------------------------------------------------------------
>
> Key: KAFKA-4882
> URL: https://issues.apache.org/jira/browse/KAFKA-4882
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Assignee: Mitch Seymour
> Labels: newbie
>
> Our internal converter configuration is shown in connect-distributed.properties and connect-standalone.properties.
> This tempts users to change it.
> In particular, they seem to believe it needs to be identical to key/value converters.
> In reality, Connect doesn't deal well with anything other than schemaless JSON as the internal converter. Users get errors and find it hard to figure out what went wrong (since this is internal, they are not expected to).
> Let's stop tempting users into shooting their own feet?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)