[
https://issues.apache.org/jira/browse/FLINK-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686413#comment-16686413
]
Chesnay Schepler commented on FLINK-10864:
------------------------------------------
I don't like the idea of introducing a separate manifest mechanism that is
entirely decoupled from the standard manifest file. I believe this is way out
of the scope of Flink (or really, anything outside the JDK) and will cause many
headaches down the line.
Uploading multiple jars is a reasonable alternative IMO.
One idea I had at times was to actually allow multiple jars to be submitted at
once; one containing the job and N for additional dependencies (kind of like a
job-scoped /lib directory). This would make it easier to re-use dependencies
across jobs. But then you're dealing with the issue of safely conveying that
"to run this jar you also have to submit X".
> Support multiple Main classes per jar
> -------------------------------------
>
> Key: FLINK-10864
> URL: https://issues.apache.org/jira/browse/FLINK-10864
> Project: Flink
> Issue Type: Improvement
> Components: Job-Submission
> Affects Versions: 1.6.2
> Reporter: Flavio Pompermaier
> Priority: Major
>
> Right now all the REST API and job submission system assumes that a jar
> contains only a single main class. In my experience this is rarely the case
> in real scenario: a jar contains multiple jobs (with similar dependencies)
> that performs different tasks.
> In our use case, for example, the shaded jar is around 200 MB and 10 jobs
> within it...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
