You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2020/01/21 09:26:00 UTC

[jira] [Commented] (FLINK-7050) RFC Compliant CSV Parser for Table Source

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

Jingsong Lee commented on FLINK-7050:
-------------------------------------

This is PRs for csv FileInputFormat/FileOutputFormat: 

[https://github.com/apache/flink/pull/9884]

[https://github.com/apache/flink/pull/10011]

FYI.

> RFC Compliant CSV Parser for Table Source
> -----------------------------------------
>
>                 Key: FLINK-7050
>                 URL: https://issues.apache.org/jira/browse/FLINK-7050
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Ecosystem
>    Affects Versions: 1.3.1
>            Reporter: Usman Younas
>            Priority: Major
>              Labels: csv, parsing, usability
>
> Currently, Flink CSV parser is not compliant with RFC 4180. Due to this issue, it was not able to parse standard csv files including double quotes and delimiters with in fields etc. 
> In order to produce this bug, we can take a csv file with double quotes included in field of the records and parse it using Flink CSV parser. One of the issue is mentioned in the jira [FLINK-4785|https://issues.apache.org/jira/browse/FLINK-4785].
> The CSV related issues will be solved by making CSV parser compliant with RFC 4180 standards for Table Source. 



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