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

Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2019/02/22 17:44:00 UTC

[jira] [Closed] (FLINK-9964) Add a CSV table format factory

     [ https://issues.apache.org/jira/browse/FLINK-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther closed FLINK-9964.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0
     Release Note: The descriptor o.a.f.table.descriptors.Csv does not describe Flink's old non-standard CSV table source/sink anymore. Instead, it can be used when writing to Kafka. The old one is still available under "org.apache.flink.table.descriptors.OldCsv" for stream/batch filesystem operations.

Fixed in 1.8.0: c3277c557aa423e7f5dd83d18b74082bf6c2bc24 & 3d07a97c82c3947935bf13b3f60aafce274a6cff

> Add a CSV table format factory
> ------------------------------
>
>                 Key: FLINK-9964
>                 URL: https://issues.apache.org/jira/browse/FLINK-9964
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: bupt_ljy
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We should add a RFC 4180 compliant CSV table format factory to read and write data into Kafka and other connectors. This requires a {{SerializationSchemaFactory}} and {{DeserializationSchemaFactory}}. How we want to represent all data types and nested types is still up for discussion. For example, we could flatten and deflatten nested types as it is done [here|http://support.gnip.com/articles/json2csv.html]. We can also have a look how tools such as the Avro to CSV tool perform the conversion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)