You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/06/21 12:58:00 UTC

[jira] [Assigned] (FLINK-28181) Add support in FlinkSessionJob to submit job using jar available in jobManager's classpath

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

Gyula Fora reassigned FLINK-28181:
----------------------------------

    Assignee: Jeesmon Jacob

> Add support in FlinkSessionJob to submit job using jar available in jobManager's classpath
> ------------------------------------------------------------------------------------------
>
>                 Key: FLINK-28181
>                 URL: https://issues.apache.org/jira/browse/FLINK-28181
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.0.0
>            Reporter: Jeesmon Jacob
>            Assignee: Jeesmon Jacob
>            Priority: Major
>
> Currently FlinkSessionJob needs to download job jar from remote endpoint (http/s3/etc.) and submit it to jobManager for starting the job. There is no built-in support for starting a job using a jar that is already available in jobManager's docker image. This ticket is created to support submitting a job using a jar that is available in jobManager's classpath.
> We have a need for team specific session cluster where all jobs are bundled in a docker image with many different configurations. For these job jars to be copied to a remote endpoint create additional maintenance and release overhead.
> Slack discussion thread: https://apache-flink.slack.com/archives/C03G7LJTS2G/p1655495665285339?thread_ts=1655495313.473359&cid=C03G7LJTS2G



--
This message was sent by Atlassian Jira
(v8.20.7#820007)