[
https://issues.apache.org/jira/browse/FLINK-28181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558476#comment-17558476
]
Jeesmon Jacob commented on FLINK-28181:
---------------------------------------
[~gyfora] Could you please help me to get started on this? As I understood
changes are:
1. Make job.jobUri and optional field
2. Add code to create a noop or empty jar
3. When jobUri is not defined and entryClass is defined, use noop/empty jar to
submit job
4. Add validation to make sure either jobUri or entryClass is defined
5. Update documentation
Thanks
> 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: New Feature
> Components: Kubernetes Operator
> 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)
