[
https://issues.apache.org/jira/browse/FLINK-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686505#comment-16686505
]
Flavio Pompermaier commented on FLINK-10864:
--------------------------------------------
No, I suggest to add an attribute to the Manifest.
Currently the PackagedProgram class only checks for the existence of
program-class or Main-Class.
I was arguing that as Flink handles program-class (that is not standard) it
could, quite easily, handle also a list of comma-separated classes in another
custom attribute. It is a reasonable trade-off I think
> 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)
