[
https://issues.apache.org/jira/browse/FLINK-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238950#comment-16238950
]
ASF GitHub Bot commented on FLINK-4272:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2732
This is still based on old runtime parts (JobManager), though the interface
allows it to be ported to the new runtime (JobMaster). As the new one is about
to supersede the old one, it might be sensible to port this to the new one
first.
> Create a JobClient for job control and monitoring
> --------------------------------------------------
>
> Key: FLINK-4272
> URL: https://issues.apache.org/jira/browse/FLINK-4272
> Project: Flink
> Issue Type: New Feature
> Components: Client, DataStream API
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
>
> The aim of this new features is to expose a client to the user which allows
> to cancel a running job, retrieve accumulators for a running job, or perform
> other actions in the future. Let's call it {{JobClient}} for now (although
> this clashes with the existing JobClient class which could be renamed to
> JobClientActorUtils instead).
> The new client should be returned from the {{ClusterClient}} class upon job
> submission. The client should also be instantiatable by the users to retrieve
> the JobClient with a JobID.
> We should expose the new JobClient to the Java and Scala APIs using a new
> method on the {{ExecutionEnvironment}} / {{StreamExecutionEnvironment}}
> called {{executeWithControl()}} (perhaps we can find a better name).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
