[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276218#comment-17276218
]
Timo Walther commented on FLINK-17793:
--------------------------------------
1) In theory it is possible to have `ResolvedSchema` in `table.api`. However, I
would consider `ResolvedSchema` similar to `ObjectIdentifier` or
`ResolvedExpression` and both of these classes are in their "more internal"
package. This also avoids confusion because we only have one kind of schema in
the API that users should use for declaration. What kind of extension do you
have in mind?
5) Identifier expansion and resolution are different topics. But as you can see
in my branch, you can create a `Schema` from a `ResolvedSchema` easily.
However, the resolved column data types are not important when storing a schema
in a catalog. Similar to views, we are storing only the rough declarative
information not the full resolved function calls.
> 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)
