You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/06/21 21:40:58 UTC
[jira] [Commented] (FLINK-2313) Change Streaming Driver Execution
Model
[ https://issues.apache.org/jira/browse/FLINK-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342789#comment-15342789 ]
Robert Metzger commented on FLINK-2313:
---------------------------------------
Another important feature here would be to make the job id, and in the yarn case also the yarn application id available.
> Change Streaming Driver Execution Model
> ---------------------------------------
>
> Key: FLINK-2313
> URL: https://issues.apache.org/jira/browse/FLINK-2313
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Stephan Ewen
>
> I would propose the following change to the Streaming Execution Environment:
> When calling {{env.execute()}}, it does not block, but return an {{ExecutionContext}} object. This execution context has various methods, that allow you to control the execution:
> - waitFor() -> Blocks until the job terminates, or the connection to the JobManager is lost.
> - stop() -> initiates a clean stop
> - cancel() -> cancels the program
> - setParallelism() -> Later: adjusts the parallelism of the program
> If this is voted as desirable, I would make a design how to do this...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)