[
https://issues.apache.org/jira/browse/KAFKA-10640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225581#comment-17225581
]
Tom Bentley commented on KAFKA-10640:
-------------------------------------
[~joshuagrisham] changes to Kafka's public API need to be done via the [KIP
process|https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals]
so you'll follow that process in order to get this change merged.
> Connect Cast and ReplaceField transforms only support top-level fields and
> Cast does not support complex types.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-10640
> URL: https://issues.apache.org/jira/browse/KAFKA-10640
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Joshua Grisham
> Priority: Major
>
> When working with anything but the most simple of messages, you will
> inevitably run into nested structures and nested fields within other
> structures. These two transforms are very important when working with data
> and if we want to use Connect for anything except the most simple scenarios
> then they should support working with more complicated structures.
> Also, in case the messages have more complicated types such as Arrays or Maps
> that are not supported by the Flatten transform, it is not possible to do
> many "standard" feeling things with the messages such as using a
> JdbcSinkConnector to put the data into a database and use it in a
> database-driven system.
> So it would be good if at a minimum we can Cast complex types as a string so
> that they can at least be sent along and stored in the database and then
> parsed later. This is opposed to them just being completely blocked like is
> the current state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
