[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276179#comment-17276179
]
Timo Walther commented on FLINK-17793:
--------------------------------------
Breaking the compatibility of {{TableColumn}} in 1.12 was a mistake. I will
make sure to fix this in the next bugfix release to make users happy.
1) I would like to fix the packaging to clearly indicate what is API. I'm also
fine to introduce a completely separate stack of classes. I think this would
also make the implementation easier. Because this hybrid resolved/unresolved
logic for computed columns and watermark spec is actually difficult to remove
without breaking compatibility.
5) Correct, `Schema` is just a DDL builder and this is what catalogs should use
as well. They should store the unresolved DDL that can also reference objects
of other catalogs.
6) Actually, we will provide only a single method and avoid confusion because
`CatalogBaseTable` doesn't provide a resolved schema and is just metadata.
> 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)
