KAFKA-5448: Change TimestampConverter configuration name to avoid conflicting with reserved 'type' configuration used by all Transformations

[ewencp]

No description provided.

[ewencp]

@dbtucker @hachikuji @gwenshap Pretty simple fix. I tested by adding

transforms=hoist,timestamp,convert
transforms.hoist.type=org.apache.kafka.connect.transforms.HoistField$Value
transforms.hoist.field=value
transforms.timestamp.type=org.apache.kafka.connect.transforms.InsertField$Value
transforms.timestamp.timestamp.field=timestamp
transforms.convert.type=org.apache.kafka.connect.transforms.TimestampConverter$Value
transforms.convert.field=timestamp
transforms.convert.target.type=string
transforms.convert.format=yyyy MM dd HH mm ss SSS z

to the file source connector and inspecting the results and things work fine (though I wouldn't mind some additional verification). At some point we'll probably want some integration tests to be able to validate things like this end-to-end, but I added unit tests for all the transformations to validate that they at least don't have any obvious conflicts that would be caught just be creating the ConnectorConfig extended with the transformations.

[dbtucker]

Thanks, @ewencp . LGTM

[gwenshap]

LGTM. Nice test collection :)

[asfbot]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5310/
Test PASSed (JDK 8 and Scala 2.12).

[asfbot]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5326/
Test PASSed (JDK 7 and Scala 2.11).