You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/05/29 02:39:00 UTC

[jira] [Closed] (FLINK-9172) Support catalogs in SQL-Client yaml config file

     [ https://issues.apache.org/jira/browse/FLINK-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bowen Li closed FLINK-9172.
---------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

merged in 1.9.0: d3e5bf69c3d3f105c1ebe7c46bd4a74e5407137f

> Support catalogs in SQL-Client yaml config file
> -----------------------------------------------
>
>                 Key: FLINK-9172
>                 URL: https://issues.apache.org/jira/browse/FLINK-9172
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Client
>            Reporter: Rong Rong
>            Assignee: Bowen Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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)