[
https://issues.apache.org/jira/browse/FLINK-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686992#comment-15686992
]
ASF GitHub Bot commented on FLINK-4272:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/2732#discussion_r89135855
--- Diff:
flink-scala/src/main/scala/org/apache/flink/api/scala/ExecutionEnvironment.scala
---
@@ -652,6 +652,34 @@ class ExecutionEnvironment(javaEnv: JavaEnv) {
}
/**
+ * Triggers the program execution. The environment will execute all
parts of the program that have
+ * resulted in a "sink" operation. Sink operations are for example
printing results
+ * [[DataSet.print]], writing results (e.g. [[DataSet.writeAsText]],
[[DataSet.write]], or other
+ * generic data sinks created with [[DataSet.output]].
+ *
+ * The program execution will be logged and displayed with a generated
default name.
+ *
+ * @return The job client of the execution to interact with the running
job.
+ */
+ def executeWithControl(): JobClient = {
+ javaEnv.executeWithControl()
+ }
+
+ /**
+ * Triggers the program execution. The environment will execute all
parts of the program that have
+ * resulted in a "sink" operation. Sink operations are for example
printing results
+ * [[DataSet.print]], writing results (e.g. [[DataSet.writeAsText]],
[[DataSet.write]], or other
+ * generic data sinks created with [[DataSet.output]].
+ *
+ * The program execution will be logged and displayed with the given
name.
+ *
+ * @return The job client of the execution to interact with the running
job.
--- End diff --
Ay!
> 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)
