[
https://issues.apache.org/jira/browse/FLINK-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686249#comment-16686249
]
Chesnay Schepler commented on FLINK-10864:
------------------------------------------
When running a jar you can specify an {{entry-class}} as documented
[here|https://ci.apache.org/projects/flink/flink-docs-master/monitoring/rest_api.html#jars-jarid-run].
Why does this not suffice your use-case?
> 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)
