[
https://issues.apache.org/jira/browse/FLINK-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622880#comment-15622880
]
ASF GitHub Bot commented on FLINK-4272:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2732
[FLINK-4272] Create a JobClient for job control and monitoring
Also includes: [FLINK-4274] Expose new JobClient in the DataSet/DataStream
API
- rename JobClient class to JobClientActorUtils
- introduce JobClient interface with two implementations
- JobClientEager: starts an actor system right away and monitors the job
- Move ClusterClient#cancel, ClusterClient#stop,
ClusterClient#getAccumulators to JobClient
- JobClientLazy: starts an actor system when requests are made by
encapsulating the eager job client
- Java and Scala API
- JobClient integration
- introduce ExecutionEnvironment#executeWithControl()
- introduce StreamExecutionEnvironment#executeWithControl()
- report errors during job execution as JobExecutionException instead of
ProgramInvocationException and adapt test cases
- provide finalizers to run code upon shutdown of client
- use ActorGateway in JobListeningContext
- add test case for JobClient implementations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-4272
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2732.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2732
----
commit a3f5cc00ec6959ca662ca925918816b4c8d984cd
Author: Maximilian Michels <[email protected]>
Date: 2016-08-21T13:25:02Z
[FLINK-4272] Create a JobClient for job control and monitoring
Also includes: [FLINK-4274] Expose new JobClient in the DataSet/DataStream
API
- rename JobClient class to JobClientActorUtils
- introduce JobClient interface with two implementations
- JobClientEager: starts an actor system right away and monitors the job
- Move ClusterClient#cancel, ClusterClient#stop,
ClusterClient#getAccumulators to JobClient
- JobClientLazy: starts an actor system when requests are made by
encapsulating the eager job client
- Java and Scala API
- JobClient integration
- introduce ExecutionEnvironment#executeWithControl()
- introduce StreamExecutionEnvironment#executeWithControl()
- report errors during job execution as JobExecutionException instead of
ProgramInvocationException and adapt test cases
- provide finalizers to run code upon shutdown of client
- use ActorGateway in JobListeningContext
- add test case for JobClient implementations
----
> 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
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 1.2.0
>
>
> 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.3.4#6332)
