[jira] [Created] (FLINK-21394) FLIP-164: Improve Schema Handling in Catalogs

["Timo Walther (Jira)" <ji...@apache.org>]

Timo Walther created FLINK-21394:
------------------------------------

             Summary: FLIP-164: Improve Schema Handling in Catalogs
                 Key: FLINK-21394
                 URL: https://issues.apache.org/jira/browse/FLINK-21394
             Project: Flink
          Issue Type: Improvement
          Components: Table SQL / API
            Reporter: Timo Walther
            Assignee: Timo Walther


Schema information is necessary at different locations in the Table API for defining tables and/or views. In particular, it is necessary to define the schema in a programmatic DDL (FLIP-129) and when converting a DataStream to a Table (FLIP-136).

We need similar APIs in the Catalog interfaces such that catalog implementations can define table/views in a unified way.

This FLIP updates the class hierarchy to achieve the following goals:

- make it visible whether a schema is resolved or unresolved and when the resolution happens
- offer a unified API for FLIP-129, FLIP-136, and catalogs
- allow arbitrary data types and expressions in the schema for watermark spec or columns
- have access to other catalogs for declaring a data type or expression via CatalogManager
- cleaned up TableSchema
- remain backwards compatible in the persisted properties and API



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