[
https://issues.apache.org/jira/browse/FLINK-27009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562716#comment-17562716
]
Thomas Weise commented on FLINK-27009:
--------------------------------------
I would prefer if any sql processing logic remains separated from the operator.
That would also mean a fat client that performs translation and requires
additional dependencies should not execute in the operator. I think that can be
accomplished by providing a separate entry point that executes in application
mode and then the user can supply any other dependencies as needed as part of
the image. Is that the plan?
> 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: Gyula Fora
> 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.10#820010)
