[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276240#comment-17276240
]
Jark Wu commented on FLINK-17793:
---------------------------------
1) I agree the `WatermarkSpec` and `TableColumn` should belong to catalog. My
only concern is how to keep compatible for this change. If we can keep
compatible, I'm fine with having them in `table.catalog`.
5) The information we rely on the resolved schema is the expanded identifiers,
not the resolved data types. My point is if we want to expose `Schema` on
CatalogBaseTable, we should provide getter methods for the members. And if we
want to provide resolved physical row data type and constraints, it would be
better to expose them on CatalogBaseTable too.
> 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)
