[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276776#comment-17276776
]
Kurt Young commented on FLINK-17793:
------------------------------------
I'm curious about `ResolvedSchema`. What exactly properties being resolved in
schema? Another thing is, right now we don't have a dedicated resolving phase
in the lifecycle of query processing, where would be the resolving take place?
I'm asking because I think we need to have very clear distinguish between
`Schema` and `ResolvedSchema`. Every one should now where to use schema and
where to use ResolvedSchema, otherwise it will still cause chaos and misuse.
> 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)
