[
https://issues.apache.org/jira/browse/FLINK-31259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701476#comment-17701476
]
Darcy Lin commented on FLINK-31259:
-----------------------------------
[~jark]
[FLIP-295|https://cwiki.apache.org/confluence/display/FLINK/FLIP-295%3A+Introduce+Pluggable+Catalog+Management]
may indeed be able to solve this problem, but I feel that it is more biased
towards catalog storage problems. If sql-gateway can support a " -i, --init
<initialization file>" parameter similar to sql-client or support a similar
"sql-gateway-defaults.yaml" configuration file similar to
[ververica-flink-sql-gateway|https://github.com/ververica/flink-sql-gateway/blob/master/conf]
can solve this problem very well. Because it is not just catalogs, it may also
involve some udf initialization and so on.
> Gateway supports initialization of catalog at startup
> -----------------------------------------------------
>
> Key: FLINK-31259
> URL: https://issues.apache.org/jira/browse/FLINK-31259
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Gateway
> Affects Versions: 1.18.0
> Reporter: Fang Yong
> Assignee: Fang Yong
> Priority: Major
>
> Support to initializing catalogs in gateway when it starts
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
