[ https://issues.apache.org/jira/browse/FLINK-17793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110191#comment-17110191 ]
Timo Walther commented on FLINK-17793: -------------------------------------- [~ykt836] I'm fine with `CatalogTableSchema`, however, it would also be used for views which is why I still would prefer just `CatalogSchema` similar to `CatalogFunction`, `CatalogPartition` etc. What do you think? > 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)