[
https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200587#comment-17200587
]
Jark Wu commented on FLINK-17793:
---------------------------------
Hi [~twalthr], I'm currently busy working on another FLIP and will have a
holiday for the following 2 weeks.
So I'm afraid I don't have enough time to finish FLIP-129 (esp. {{Schema}}
class) in time.
In general, I'm fine with unifying {{Schema}} and {{CatalogSchema}}, but we may
need a new kind of {{Expression}} for sql expression?
> 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)
