[
https://issues.apache.org/jira/browse/FLINK-19949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated FLINK-19949:
-------------------------------
Description:
We should unescape the line delimiter characters first because the DDL can be
read from a file. So that the new line "\n" in the DDL options was recognized
as 2 characters.
While what user want is actually the invisible new line character.
{code:sql}
create table t1(
...
) with (
'format' = 'csv',
'csv.line-delimiter' = '\n'
...
)
{code}
Same as the field delimiter.
was:
We should unescape the line delimiter characters first because the DDL can be
read from a file. So that the new line "\n" in the DDL options was recognized
as 2 characters.
While what user want is actually the invisible new line character.
{code:sql}
create table t1(
...
) with (
'format' = 'csv',
'csv.line-delimiter' = '\n'
...
)
{code}
> Unescape CSV format line and field delimiter character
> ------------------------------------------------------
>
> Key: FLINK-19949
> URL: https://issues.apache.org/jira/browse/FLINK-19949
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.11.2
> Reporter: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> We should unescape the line delimiter characters first because the DDL can be
> read from a file. So that the new line "\n" in the DDL options was recognized
> as 2 characters.
> While what user want is actually the invisible new line character.
> {code:sql}
> create table t1(
> ...
> ) with (
> 'format' = 'csv',
> 'csv.line-delimiter' = '\n'
> ...
> )
> {code}
> Same as the field delimiter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
