[ https://issues.apache.org/jira/browse/FLINK-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650988#comment-15650988 ]
ASF GitHub Bot commented on FLINK-4272: --------------------------------------- Github user tillrohrmann commented on a diff in the pull request: https://github.com/apache/flink/pull/2732#discussion_r87102646 --- Diff: flink-runtime/src/main/scala/org/apache/flink/runtime/minicluster/FlinkMiniCluster.scala --- @@ -485,6 +485,52 @@ abstract class FlinkMiniCluster( } @throws(classOf[JobExecutionException]) + def submitJob( + jobGraph: JobGraph, + printUpdates: Boolean) --- End diff -- The current Flink Scala style indents parameters twice and the return type once: ``` def foobar( x: Int, y: Float) : Double = { ... } ``` > 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)