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

ASF GitHub Bot commented on FLINK-8316:
---------------------------------------

Github user xccui commented on the issue:

    https://github.com/apache/flink/pull/5210
  
    Hi @sunjincheng121, thanks for your reply. I think an example would be 
that, for some non-standard CSV files like `a, b , c,`, if the boolean flag 
`trailingDelimiter=false`, the file will be parsed with 4 fields; while if 
`trailingDelimiter=true`, the file will be parsed with 3 fields, in which the 
trailing delimiter `,` is omitted. Further, the trailing delimiter could be set 
as another character, e.g., `a, b, c;`.


> The CsvTableSink and the CsvInputFormat are not in sync
> -------------------------------------------------------
>
>                 Key: FLINK-8316
>                 URL: https://issues.apache.org/jira/browse/FLINK-8316
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>            Reporter: Xingcan Cui
>            Assignee: Xingcan Cui
>            Priority: Major
>
> As illustrated in [this 
> thread|https://lists.apache.org/thread.html/cfe3b1718a479300dc91d1523be023ef5bc702bd5ad53af4fea5a596@%3Cuser.flink.apache.org%3E],
>  the format for data generated in {{CsvTableSink}} is not compatible with 
> that accepted by {{CsvInputFormat}}. We should unify their trailing 
> delimiters.



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

Reply via email to