[
https://issues.apache.org/jira/browse/FLINK-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020090#comment-17020090
]
Aljoscha Krettek commented on FLINK-7050:
-----------------------------------------
I'm posting this to all the format-relevant issues, it possibly also applies
here: Before working on Table API formats, we need to figure out the
interaction of serialization formats and sources. Currently we don't support
reading from source metadata, among other things. Please wait on this issue
until those things are resolved or reach out to me or [~dwysakowicz] before
starting on this.
> 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)
