[
https://issues.apache.org/jira/browse/FLINK-15223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995415#comment-16995415
]
Jingsong Lee commented on FLINK-15223:
--------------------------------------
After offline discussion with [~danny0405] . We should not unescape java in
planner.
Consider DDL, there are three entrances:
# tableEnv.sqlUpdate, this is Java interface, in Java world, we can write \n,
so there is no reason to unescape.
# Yaml, Yaml parser will help us to unescape text file, because in text file,
user can not write \n
# Sql client, from user shell command, we should unescape DDL text even DML
text.
So, the real problem is 3, we should fix Sql client.
> 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
> Assignee: Jingsong Lee
> 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)
