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

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-21394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-21394:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned  (was: auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> 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.20.1#820001)