[
https://issues.apache.org/jira/browse/FLINK-22787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352443#comment-17352443
]
Timo Walther commented on FLINK-22787:
--------------------------------------
Maybe I'm repeating myself, but this is another example of an architectural
issue. We should not come up with multiple parsers but rely on and improve the
main Flink SQL parser extended from Calcite.
> Fix parse error when input statement has inline comments
> --------------------------------------------------------
>
> Key: FLINK-22787
> URL: https://issues.apache.org/jira/browse/FLINK-22787
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Client
> Affects Versions: 1.13.0
> Reporter: Shengkai Fang
> Priority: Major
>
> You can reproduce this problem by using
> {code:java}
> CREATE TABLE test(
> a INT
> ); -- comment with ;
> {code}
> It might need us to introduce a simple parser to clean up. The parser only
> has tokens, e.g. identifier, string, comment. In this case, we don't need to
> rely the grammar in the SqlParser.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
