Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Tue, 21 Jun 2016 22:03:58 +0000 (UTC)
From: "Gyula Fora (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12842272.1435830751000.16657.1466546638093@Atlassian.JIRA>
In-Reply-To: <JIRA.12842272.1435830751000@Atlassian.JIRA>
References: <JIRA.12842272.1435830751000@Atlassian.JIRA> <JIRA.12842272.1435830751676@arcas>
Subject: [jira] [Commented] (FLINK-2313) Change Streaming Driver Execution
 Model
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Jun 2016 22:03:59 -0000


    [ https://issues.apache.org/jira/browse/FLINK-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342845#comment-15342845 ] 

Gyula Fora commented on FLINK-2313:
-----------------------------------

Btw, do you have any thoughts on how should this behave in case of job failures/restarts etc? This is also related to Robert's question regarding the job id.

> 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)