[
https://issues.apache.org/jira/browse/FLINK-31425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700078#comment-17700078
]
Chesnay Schepler commented on FLINK-31425:
------------------------------------------
??However it also seems to bring in some confusion and 'blackbox' feeling in
that the payload of rest api is a binary object??
It's not intended to be used by anything but the client.
??Do you think it make more sense to build an api that accepts streamgraph as
input which may be presented with a json??
That JSON would still have to contain many binary blobs for the user-code.
While there has been a desire for a more language-agnostic way to submit jobs I
don't see this as being the way to do it. Expanding the API more without a
particularly strong benefit doesn't make much sense to me.
> Support submitting a job with streamgraph
> ------------------------------------------
>
> Key: FLINK-31425
> URL: https://issues.apache.org/jira/browse/FLINK-31425
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream
> Reporter: Jeff
> Priority: Major
>
> Currently, we have rest api to submit a job via jobgraph, which is aligned to
> the way of flink cli running the entry class locally and submit the compiled
> binary to remote cluster for execution.
> This is convenient in its own right. However it also seems to bring in some
> confusion and 'blackbox' feeling in that the payload of rest api is a binary
> object and thus not self-descriptive and it's relative a low-level
> presentation of the job executions whose interface is more likely to change
> as version evolves.
> Do you think it make more sense to build an api that accepts streamgraph as
> input which may be presented with a json(just like visualizer did for an
> execution plan visualization) plus additional runtime related configs and
> resources? This may make the rest interface more descriptive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
