[
https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596562#comment-16596562
]
Eron Wright commented on FLINK-9172:
-------------------------------------
[~twalthr] do you agree that we need to extend the environment file to register
external catalogs? Assumedly the catalog factory would require some connection
info and related parameters. Likewise we may need a set of descriptors to
provide a typed API. In other words, the pattern that was established for
sources could now be applied to catalogs.
Maybe a design doc should be written to allow for further discussion on this.
BTW I am very much looking forward to this feature, and would like to help.
Here's the scenario that I have in mind: to be able to develop a library for a
particular domain, that defines a catalog of tables that relate to that domain.
Then, use that library in Java/Scala programs and in the SQL Client. In
other words, catalogs provide a unified way to define a set of tables. WDYT?
> 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)
