[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276385#comment-17276385
]
Timo Walther commented on FLINK-17793:
--------------------------------------
5) Providing getter methods for the members of `Schema` sounds good to me. We
will also need a way of converting a `Schema` into properties for persisting.
`CatalogBaseTable` is a pure metadata object, it doesn't need a resolved
resolved physical row data type and constraints. The `CatalogManager` will take
care of resolving the schema (this is similar to the current architecture in
`CatalogManager#resolveTableSchema`) and provide the resolved schema where
necessary.
> 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)
