You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zili Chen (Jira)" <ji...@apache.org> on 2019/11/30 02:25:00 UTC

[jira] [Commented] (FLINK-14854) Add executeAsync() method to execution environments

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

Zili Chen commented on FLINK-14854:
-----------------------------------

I notice that for batch code path, it is easy we introduce a {{executeAsync(jobName?)}} method while in streaming code path things become a bit tricky that we modify StreamGraph after compilation in blink planner. Trying to find a clean way for extend asynchronous version {{execute}} in streaming code path, falling back to add {{@Internal executeAsync(StreamGraph)}}.

> Add executeAsync() method to execution environments
> ---------------------------------------------------
>
>                 Key: FLINK-14854
>                 URL: https://issues.apache.org/jira/browse/FLINK-14854
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataSet, API / DataStream
>            Reporter: Aljoscha Krettek
>            Assignee: Zili Chen
>            Priority: Major
>
> The new {{executeAsync()}} method should return a {{JobClient}}. This exposes the new executor/job client work on the user API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)