[
https://issues.apache.org/jira/browse/FLINK-31603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709664#comment-17709664
]
Jark Wu edited comment on FLINK-31603 at 4/7/23 11:36 AM:
----------------------------------------------------------
Hi [~paul8263], this is an expected behavior in SQL, because there is indeed a
line break in the string literal. MySQL and other databases also have the same
behavior.
{code}
mysql> select 'abc
edf' as str;
+---------+
| str |
+---------+
| abc
edf |
+---------+
1 row in set (0.01 sec)
{code}
was (Author: jark):
Hi [~paul8263], this is an expected behavior in SQL, because there is indeed a
line break in the string literal. MySQL and other databases also have the same
behavior.
{code}
mysql> select 'abc
edf';
+---------+
| abc
edf |
+---------+
| abc
edf |
+---------+
1 row in set (0.01 sec)
{code}
> Line break should be removed in create table with-clauses, load module
> with-clauses and table hints for both keys and values
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-31603
> URL: https://issues.apache.org/jira/browse/FLINK-31603
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.16.0, 1.16.1
> Environment: Flink 1.16.0
> Reporter: Yao Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> Given a SQL like this:
> {code:sql}
> CREATE TABLE MyTable (
> `user_id` BIGINT,
> `name` STRING,
> `timestamp` TIMESTAMP_LTZ(3) METADATA
> ) WITH (
> 'connector' = 'kaf
> ka'
> ...
> );
> {code}
> After parsing the SQL, the option value 'connector' is 'kaf\nka', which will
> lead to problems.
> The line break inside keys/values in with-clauses and table hints should be
> removed when parsing SQLs.
> If this is the issue that needs to fix, I would like to do it, as I am
> currently working on it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
