You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "silence (Jira)" <ji...@apache.org> on 2020/10/15 06:07:00 UTC

[jira] [Commented] (FLINK-19652) Support pure string format for Kafka table connector

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

silence commented on FLINK-19652:
---------------------------------

it looks similar with this issue https://issues.apache.org/jira/projects/FLINK/issues/FLINK-14356

> Support pure string format for Kafka table connector
> ----------------------------------------------------
>
>                 Key: FLINK-19652
>                 URL: https://issues.apache.org/jira/browse/FLINK-19652
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / Kafka, Formats (JSON, Avro, Parquet, ORC, SequenceFile)
>    Affects Versions: 1.11.0, 1.11.1, 1.11.2
>            Reporter: Qingsheng Ren
>            Priority: Major
>
> Currently Kafka table connector supports some formats including CSV, JSON, Avro etc., but there are still cases that users want to deserialize the entire record as a string and parse with UDTF by themselves. 
> A hacky way is defining a Kafka source table with only one string column and still using CSV format, but to use a character that will never appear in the message as the field delimiter. Actually it's hard to find such a delimiter if user cannot control the source of data. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)