[
https://issues.apache.org/jira/browse/FLINK-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694568#comment-16694568
]
Chesnay Schepler commented on FLINK-10862:
------------------------------------------
This issue is related to FLINK-10864 in that it asks the same question: How
usable should Flink itself be as an artifact management system; i.e. a system
that allows the upload&storage of jars with attached versioning, metadata etc. .
I would like rid Flink completely of that notion and only provide a primitive
for submitting jars; basically have the REST API jar submission work the exact
same way as when going through the CLI. No storing of jars, no descriptions;
basically just combine the submit&run call into a single action and remove all
the other stuff with the exception of the plan preview.
We have to cut down on the scope of Flink as we are already active in so many
orthogonal areas (supporting X container environments, Y libraries, Z
connectors).
The jar management stuff we can get rid of; an open-source solution for such
(like you proposed on FLINK-10864) would be sufficient to cover most use-cases.
This would remove quite a bit of complexity from the REST API, WebUI and
overall jar execution code, which ultimately gave rise to issues like
FLINK-10879.
> REST API does not show program descriptions of "simple" ProgramDescription
> --------------------------------------------------------------------------
>
> Key: FLINK-10862
> URL: https://issues.apache.org/jira/browse/FLINK-10862
> Project: Flink
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.6.2
> Reporter: Flavio Pompermaier
> Priority: Major
> Labels: rest_api
>
> When uploading a jar containing a main class implementing ProgramDescription
> interface, the REST API doesn't list its description. It works only if the
> class implements Program (that I find pretty useless...why should I return
> the plan?)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
