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

["David Tucker (JIRA)" <ji...@apache.org>]

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

David Tucker commented on KAFKA-5448:
-------------------------------------

I'd suggest something like "target.type" or "output.type", to make it very clear that the transformation takes in the serialized DATE format and writes out a new data type.


> 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
>
>   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)