[
https://issues.apache.org/jira/browse/FLINK-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther updated FLINK-13335:
---------------------------------
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))
was: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.
> Bring the SQL CREATE TABLE DDL closer to FLIP-37
> ------------------------------------------------
>
> Key: FLINK-13335
> URL: https://issues.apache.org/jira/browse/FLINK-13335
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Timo Walther
> Assignee: Danny Chan
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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))
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
