[
https://issues.apache.org/jira/browse/FLINK-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368047#comment-17368047
]
Ingo Bürk edited comment on FLINK-22998 at 6/23/21, 8:18 PM:
-------------------------------------------------------------
Unquoted key/value in the Calcite parser unfortunately isn't easy, because keys
and values would be parsed as identifiers, but identifiers have much stricter
syntax than the keys and values in Flink. That's why we decided to use quotes
for SET, the unquoted syntax is deprecated and will be removed in a future
release. See FLINK-22848.
However, there's other custom things in the extended parser still as well.
was (Author: airblader):
Unquoted key/value in the Calcite parser unfortunately isn't easy, because keys
and values would be parsed as identifiers, but identifiers have much stricter
syntax than the keys and values in Flink. That's why we decided to use quotes
for SET, the unquoted syntax is deprecated and will be removed in a future
release.
However, there's other custom things in the extended parser still as well.
> Flink SQL does not support block comment before SET command
> -----------------------------------------------------------
>
> Key: FLINK-22998
> URL: https://issues.apache.org/jira/browse/FLINK-22998
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.14.0
> Reporter: Zhiwen Sun
> Priority: Major
>
> Flink SQL does not support block comment before SET command.
> A tiny SQL that produces the bug:
>
> {code:java}
> /**
> comment
> **/
> SET sql-client.execution.result-mode=TABLEAU;
> SELECT 'hello';{code}
>
> while following SQL works fine:
>
> {code:java}
> SET sql-client.execution.result-mode=TABLEAU;
> /**
> comment
> **/
> SELECT 'hello';{code}
>
>
> After I debug Flink source code, I found that EXTENDED_PARSER does not
> support block comment.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
