[
https://issues.apache.org/jira/browse/FLINK-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686368#comment-16686368
]
Flavio Pompermaier commented on FLINK-10864:
--------------------------------------------
I don't suggest to scan the entire jar, just to use a different manifest entry
(like *Other-Main-Classes* or *Main-classes*). E.g:
*Main-Class:* org.apache.flink.WordCount
*Other-Main-Classes*:
org.apache.flink.WordCount2,org.apache.flink.WordCount3,org.apache.flink.WordCount4
or
*Main-Classes:*
org.apache.flink.WordCount,org.apache.flink.WordCount2,org.apache.flink.WordCount3,org.apache.flink.WordCount4
Then, the org.apache.flink.client.program.PackagedProgram class should just
look for this extra tag and handle it.
> 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)
