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 2019/12/13 02:28:00 UTC
[jira] [Comment Edited] (FLINK-15223) Csv connector should unescape
delimiter parameter characters
[ https://issues.apache.org/jira/browse/FLINK-15223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995290#comment-16995290 ]
Jingsong Lee edited comment on FLINK-15223 at 12/13/19 2:27 AM:
----------------------------------------------------------------
I prefer unescapeJava for all DDL properties. (In the "with" block)
What do you think? [~jark] [~ykt836]
was (Author: lzljs3620320):
I prefer unescapeJava for all DDL properties. (In the "with" block)
> Csv connector should unescape delimiter parameter characters
> ------------------------------------------------------------
>
> Key: FLINK-15223
> URL: https://issues.apache.org/jira/browse/FLINK-15223
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Jark Wu
> Priority: Blocker
> Fix For: 1.10.0
>
>
> As described in documentation[1], a csv format can use {{'format.line-delimiter' = '\n'}} to specify line delimiter. However, the property value is parsed into two characters "\n" , this result to reading failed. There is no workaround for now, unless fix it. The delimiter should be unescaped, e.g. using {{StringEscapeUtils.unescapeJava}}. Note that both old csv and new csv have the same problem, and both {{field-delimiter}} and {{line-delimiter}}.
> [1]: https://ci.apache.org/projects/flink/flink-docs-master/dev/table/connect.html#old-csv-format
--
This message was sent by Atlassian Jira
(v8.3.4#803005)