[
https://issues.apache.org/jira/browse/FLINK-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651009#comment-15651009
]
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_r87100355
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/ExecutionEnvironment.java ---
@@ -911,6 +912,24 @@ public JobExecutionResult execute() throws Exception {
public abstract JobExecutionResult execute(String jobName) throws
Exception;
/**
+ * Triggers the program execution, just like {@code execute()} but does
not block.
+ * Instead, it returns a JobClient which can be used to interact with
the running job.
+ * @return A JobClient for job interaction.
+ * @throws Exception Thrown if the program submission fails.
+ */
+ public JobClient executeWithControl() throws Exception {
+ return executeWithControl(getDefaultName());
+ }
+
+ /**
+ * Triggers the program execution, just like {@code execute(String
jobName)} but does not block.
+ * Instead, it returns a JobClient which can be used to interact with
the running job.
+ * @return A JobClient for job interaction.
+ * @throws Exception Thrown if the program submission fails.
+ */
+ public abstract JobClient executeWithControl(String jobName) throws
Exception;
--- End diff --
I'm not sure whether `executeWithControl` is the best name for this method
given that it's going to be part of the public API. I don't have a perfect
alternative but what about `executedAttached` or `submitJob`?
> 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)
