[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277012#comment-17277012
]
Timo Walther commented on FLINK-17793:
--------------------------------------
[~ykt836] We resolve data types and expressions. Regarding expressions, we are
performing a resolution step already in the code base. Please take a look at
{{org.apache.flink.table.catalog.CatalogManager#resolveTableSchema}} and
{{org.apache.flink.table.api.internal.CatalogTableSchemaResolver}}. The
confusing part here is that both resolved and unresolved schema are represented
as {{TableSchema}} so it is never visible if a schema has been resolved already
or not.
> 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)
