[
https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676117#comment-16676117
]
Xuefu Zhang commented on FLINK-9172:
------------------------------------
Hi [~walterddr], thanks for chiming in. I don't think we are limiting the scope
to supporting for Hive catalog only. While there is a bigger initiative beyond
what the task is for, from my understanding I think the task itself is to allow
user to specify catalogs in the config file and designate one as the default.
This is quite limited in scope, I'm open to the idea of a design doc. I'm also
open to an intermediate approach before the unified connector APIs are in place
because it may take time to materialize.
As an FYI, I was brought here by FLINK-10759, which was mark as dupe of this.
Let me know if you have additional thoughts on this.
> 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)
