[
https://issues.apache.org/jira/browse/FLINK-31425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699925#comment-17699925
]
Junrui Li commented on FLINK-31425:
-----------------------------------
[~tophei] Thanks for creating this issue. IIUC, according to the description, I
think this issue can be divided into two parts:
1. Submit and run jobs by submitting a streamGraph, which is very meaningful.
Submitting and running jobs through streamGraph can expand the dynamic
adjustment capability of flink runtime. This is a relatively large and very
meaningful change, and we are currently doing related research.
2. Make StreamGraph public so that users can get streamGraph. I'm not sure if
this part has enough meaning to expose an internal interface to users, which
may bring additional burden.
> 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)
