[jira] [Created] (FLINK-16183) Make identifier parsing in Table API more lenient

["Dawid Wysakowicz (Jira)" <ji...@apache.org>]

Dawid Wysakowicz created FLINK-16183:
----------------------------------------

             Summary: Make identifier parsing in Table API more lenient
                 Key: FLINK-16183
                 URL: https://issues.apache.org/jira/browse/FLINK-16183
             Project: Flink
          Issue Type: Improvement
          Components: Table SQL / API
            Reporter: Dawid Wysakowicz
            Assignee: Dawid Wysakowicz
             Fix For: 1.11.0


I suggest to make the parsing logic for identifiers in Table API more lenient. We should not require users to escape any sql identifiers. 

It will make the identifiers not cross compatible between Table API and SQL, but it will improve user's experience and also will let us support parsing identifiers coming from Java's ExpressionParser (e.g. for a string array(..) it produces a lookup call with an "array" identifier which should be parsed)

I suggest doing it by extending the FlinkSqlParserImpl with a new logic for TableApiSqlIdentifier which would be very similar to CompoundIdentifier with slightly adjusted logic which would not discard reserved keywords.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)