[
https://issues.apache.org/jira/browse/KAFKA-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-4882:
-----------------------------------------
Fix Version/s: (was: 0.10.2.1)
Removing fix version since this isn't actually a critical bug fix for 0.10.2.1
and doesn't need to be scheduled for a specific release. The fix version can be
set automatically when the patch is merged.
[~mitch-seymour] Normally we'd just leave the fix version blank until patches
get merged unless the issue is a blocker for a specific release (whether due to
being a critical bug or because we're scheduling changes that need to go into a
specific release, e.g. needs to happen in a major release version).
> 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)
