You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Biao Geng (Jira)" <ji...@apache.org> on 2022/06/06 02:21:00 UTC
[jira] [Commented] (FLINK-27009) Support SQL job submission in flink kubernetes opeartor
[ https://issues.apache.org/jira/browse/FLINK-27009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550265#comment-17550265 ]
Biao Geng commented on FLINK-27009:
-----------------------------------
Hi [~mbalassi] , sorry for the late reply. I have finished the [poc|https://github.com/bgeng777/flink/commit/5b4338fe52ec343326927f0fc12f015dd22b1133] that directly utilizes the sql client. But it turns out that I need more time to initial the draft of FLIP. Will notify you once I finish it.
> Support SQL job submission in flink kubernetes opeartor
> -------------------------------------------------------
>
> Key: FLINK-27009
> URL: https://issues.apache.org/jira/browse/FLINK-27009
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Biao Geng
> Assignee: Biao Geng
> Priority: Major
>
> Currently, the flink kubernetes opeartor is for jar job using application or session cluster. For SQL job, there is no out of box solution in the operator.
> One simple and short-term solution is to wrap the SQL script into a jar job using table API with limitation.
> The long-term solution may work with [FLINK-26541|https://issues.apache.org/jira/browse/FLINK-26541] to achieve the full support.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)