[
https://issues.apache.org/jira/browse/KAFKA-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shikhar Bhushan resolved KAFKA-4068.
------------------------------------
Resolution: Not A Problem
I was thinking JSON since it would be easy to serialize to a human-readable
format with that. But if we want to implement a more useful
{{Struct.toString()}} in any case for debugging purposes, we should probably do
that instead. Fair point about keeping the file sink connector as simple as
possible. Closing this in favor of KAFKA-4070.
> FileSinkTask - use JsonConverter to serialize
> ---------------------------------------------
>
> Key: KAFKA-4068
> URL: https://issues.apache.org/jira/browse/KAFKA-4068
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Shikhar Bhushan
> Assignee: Shikhar Bhushan
> Priority: Minor
>
> People new to Connect often try out hooking up e.g. a Kafka topic with Avro
> data to the file sink connector, only to find the file contain values like:
> {noformat}
> org.apache.kafka.connect.data.Struct@ca1bf85a
> org.apache.kafka.connect.data.Struct@c298db6a
> org.apache.kafka.connect.data.Struct@44108fbd
> {noformat}
> This is because currently the {{FileSinkConnector}} is meant as a toy example
> that expects the schema to be {{Schema.STRING_SCHEMA}}, though it just
> {{toString()}}'s the value without verifying that.
> A better experience would probably be if we used
> {{JsonConverter.fromConnectData()}} for serializing to the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
