Affects Version/s: None
Fix Version/s: 1.9.0
Component/s: Table SQL / API
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.
This brings the SQL DDL closer to FLIP-37. However, there are a couple of known limitations.
Currently unsupported features:
- ROW with comments
- 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))