You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/08/19 04:02:00 UTC

[jira] [Commented] (FLINK-17793) Replace TableSchema with dedicated CatalogSchema

    [ https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180247#comment-17180247 ] 

Jark Wu commented on FLINK-17793:
---------------------------------

Hi [~twalthr], are you still working on this? Do you think we should have this in 1.12? 

> Replace TableSchema with dedicated CatalogSchema
> ------------------------------------------------
>
>                 Key: FLINK-17793
>                 URL: https://issues.apache.org/jira/browse/FLINK-17793
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>
> The {{TableSchema}} is used for representing the schema of catalog table and the schema of a {{Table}} object and operation. We should split those responsibilities both for a cleaner API and long-term separation of concerns. Connectors should work on a CatalogSchema instead.



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