[
https://issues.apache.org/jira/browse/FLINK-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686655#comment-16686655
]
Flavio Pompermaier commented on FLINK-10864:
--------------------------------------------
If you look at the JarListInfo, the class returned by the /jars REST API, you
can see that it was meant to support multiple main classes in a single jar (in
contains a List<JarEntryInfo>). If I had to write this API I would also add a
description of the job parameters/options.
I understand that removing complexity from the code is always good but this
looks like a step back to me.
Why not supporting 2 different flavors of *Main-Class*? One that does not
implement any interface (and thus does not provide any info like it is now) and
one that implement a "brand new" interface FlinkJob which has at least 2
methods: getDescrition() and List<Option> getJobParameters()?
In this way you can get rid of the legacy Program and ProgramDescription
interfaces and read only a the Main-Class attribute from the Manifest..
> 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)
