[
https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596917#comment-16596917
]
Rong Rong commented on FLINK-9172:
----------------------------------
[~eronwright] as far as I know, similar to table source and sink. User should
be able to define catalogs either as default environment. Or defined in
extended user sessions. And yes catalog factories require specific information
in order to establish connections.
Originally when I created the ticket we were trying to add both HCatalog and
one of our in-house catalog when using Flink, thus we propose to have a general
API to create ExternalCatalog based on different configurations.
as [~twalthr] mentioned, catalog support has already been added in, on the
flink-table side, we just need to add a {{TableCatalogFactory}} that extends
{{TableFactory}} and returns an instance of {{ExternalCatalog}}. On the
SQL-client side, what we had in mind was similar to how {{TableFactoryService}}
is used to discover {{TableFactory}}, user can register a similar
{{TableCatalogFactoryService}} that is used to discover
{{TableCatalogFactory}}. and SQL-client will use this configuration information
to locate the correct {{TableCatalogFactory}} and ultimately instantiate the
external catalog instance.
I do agree we need a design doc for at least how the configuration should look
like. I will try come up with a POC and a short configuration mock up. What do
you guys think?
> 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
> Reporter: Rong Rong
> Assignee: Rong Rong
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
