You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Feng Jin (Jira)" <ji...@apache.org> on 2022/11/24 18:09:00 UTC

[jira] [Commented] (FLINK-30126) Delay registration of the catalog, register the catalog as needed

    [ https://issues.apache.org/jira/browse/FLINK-30126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638382#comment-17638382 ] 

Feng Jin commented on FLINK-30126:
----------------------------------

We are currently facing a similar problem. Our current solution: In version 1.12, we will analyze SQL node tree to find which catalogs are used in the SQL  and then register the catalogs in tableEnv. In 1.14, the catalog will be verified in the grammar parser stage. We must use other means to detect the used catalogs, such as through string matching, and then register the required catalog in advance before running SQL.   

 

My initial thoughts, is it possible to add some interface to CatalogManager to extend the behavior of catalog  ? 

> Delay registration of the catalog, register the catalog as needed
> -----------------------------------------------------------------
>
>                 Key: FLINK-30126
>                 URL: https://issues.apache.org/jira/browse/FLINK-30126
>             Project: Flink
>          Issue Type: New Feature
>            Reporter: melin
>            Priority: Major
>
> Data platform has registered many relational database data sources such as mysql, data source code is used as the catalog name, we are not sure which data source needs to register the catalog in flink, we hope that the required catalog can be dynamically loaded when sql is executed, flink provides the interface. Users can customize the registration catalog



--
This message was sent by Atlassian Jira
(v8.20.10#820010)