[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180359#comment-17180359
]
Timo Walther commented on FLINK-17793:
--------------------------------------
I'm also not sure yet. But it would be good to avoid too many schema's. I'm
reusing `Schema` in FLIP-136 to have at least all main API parts using the same
`Schema` class. It could qualify also as a `CatalogSchema` if we add support
for SQL expressions. We could think about a new expression like
{{.select($("s"), lit(12).plus(3), sql("CAST(s AS VARCHAR)"))}} this could be
handy for users that want to use SQL from time to time in the Table API.
> 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)
