[
https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674101#comment-16674101
]
Rong Rong commented on FLINK-9172:
----------------------------------
Hi [~xuefuz] I think the scope of this JIRA goes beyond supporting for Hive
catalog only. There were also some discussions relevant to this on [~twalthr]'s
recent proposal for unified SQL connector API.
We also have some internal implementations for this JIRA that works on our
proprietary catalog system in house. I've summarized some of my very higher
level insights previously as well. Maybe a short design doc regarding this
configuration can be drafted to align the goals and together? What do you guys
think [~suez1224] [~xuefuz].
> Support external catalog factory that comes default with SQL-Client
> -------------------------------------------------------------------
>
> Key: FLINK-9172
> URL: https://issues.apache.org/jira/browse/FLINK-9172
> Project: Flink
> Issue Type: Sub-task
> Components: SQL Client
> Reporter: Rong Rong
> Assignee: Eron Wright
> Priority: Major
>
> It doesn't seem that the configuration (YAML) file allows specifications of
> external catalogs currently. The request here is to add support for external
> catalog specifications in YAML file. User should also be able to specify one
> catalog is the default.
> It will be great to have SQL-Client to support some external catalogs
> out-of-the-box for SQL users to configure and utilize easily. I am currently
> think of having an external catalog factory that spins up both streaming and
> batch external catalog table sources and sinks. This could greatly unify and
> provide easy access for SQL users.
> The catalog-related configurations then need to be processed and passed to
> TableEnvironment accordingly by calling relevant APIs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
