You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2017/06/14 22:25:00 UTC

[jira] [Resolved] (KAFKA-5448) TimestampConverter's "type" config conflicts with the basic Transformation "type" config

     [ https://issues.apache.org/jira/browse/KAFKA-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gwen Shapira resolved KAFKA-5448.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.1.0

Issue resolved by pull request 3342
[https://github.com/apache/kafka/pull/3342]

> TimestampConverter's "type" config conflicts with the basic Transformation "type" config
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5448
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5448
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Ewen Cheslack-Postava
>            Priority: Blocker
>             Fix For: 0.11.0.0, 0.11.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> [KIP-66|https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect] defined one of the configs for TimestampConverter to be "type". However, all transformations are configured with the "type" config specifying the class that implements them.
> We need to modify the naming of the configs so these don't conflict.



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