[
https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676222#comment-16676222
]
Rong Rong commented on FLINK-9172:
----------------------------------
Thanks for the info [~xuefuz]. I wasn't aware that this ticket was becoming
part of the Hive metastore initiative. I think we can create a limited scope to
just implement a way to specify catalogs and with default support for HCatalog
(probably FLINK-10699?). However, I wasn't sure having an intermediate solution
before the unified connector API design getting finalized.
AFAIK there are several questions/discussions still pending in
https://docs.google.com/document/d/1Yaxp1UJUFW-peGLt8EIidwKIZEWrrA-pznWLuvaH39Y/edit#heading=h.khiicuym1198
and it would be pretty painful if the final specification of the SQL-client
interface differs from the intermediate design. I am leaning towards creating a
more detail design doc on this based on the discussion in the google doc first.
What do you think [~twalthr] ?
> 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)
