Jeff created FLINK-31425:
----------------------------
Summary: 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
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)
