[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276200#comment-17276200
]
Jark Wu commented on FLINK-17793:
---------------------------------
1) Is it possible to move `ResolvedSchema` to `table.api`? Then we may not have
the re-packaging problem. It seems strange that the unresolved `Schema` in
located in `table.api`, but the `ResolvedSchema` is in `table.catalog`. I know
`ResolvedSchema` is only used in catalog related classes for now, but will it
be extended in the future?
5) "They should store the unresolved DDL"
Is that true? From my understanding, we should store the resolved computed
column expression and watermark expression (expanding identifiers) just like
how we store views.
> 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)
