[FLINK-13335] Bring the SQL CREATE TABLE DDL closer to FLIP-37

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Table SQL / API
• Labels: pull-request-available

Release Note

The identifiers "string" and "bytes" are reserved keywords now and will be used for data types in the future. In case of SQL statements with a function, field, or table name, those identifiers need to be enclosed in backticks: `STRING` or `BYTES`.

• Assignee: Danny Chen
• Reporter: Timo Walther
• Created: 19/Jul/19 07:50
• Updated: 02/Aug/19 15:21
• Resolved: 02/Aug/19 15:21

Description

At a first glance it does not seem that the newly introduced DDL is compliant with FLIP-37. We should ensure consistent behavior esp. also for corner cases.

Update:
This brings the SQL DDL closer to FLIP-37. However, there are a couple of known limitations.

Currently unsupported features:

• INTERVAL
• ROW with comments
• ANY
• NULL
• NOT NULL/NULL for top-level types
• ignoring collation/charset
• VARCHAR without length (=VARCHAR(1))
• TIMESTAMP WITH TIME ZONE
• user-defined types
• data types in non-DDL parts (e.g. CAST(f AS STRING))

Issue Links

• links to: GitHub Pull Request #9243