[
https://issues.apache.org/jira/browse/FLINK-31425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702472#comment-17702472
]
Jeff commented on FLINK-31425:
------------------------------
Thanks [~JunRuiLi] and [~chesnay] for the insight.
For item 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'
This is proposed to serve as alternative interface to JobGraph based api. Agree
it's sort of internal interface, but it's a relative higher level abstraction
compared with JobGraph and should be more developer friendly.
[~chesnay] some existing integration like Beam Flink Runner has to leverage on
JobGraph interface for job submission,
[https://github.com/apache/beam/blob/master/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineExecutionEnvironment.java#L136,]
where it appears like a blackbox and not feasible for some runtime check or
debug log maybe. That makes me think whether a StreamGraph based interface can
make more sense.
By the way, do we have some FLIP or mail thread that tracks discussion of
'language-agnostic way to submit jobs'.
> 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)
