[
https://issues.apache.org/jira/browse/FLINK-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977291#comment-16977291
]
Zili Chen edited comment on FLINK-14854 at 11/19/19 9:21 AM:
-------------------------------------------------------------
In previous discussion we separate the stage into
1. submit job -> {{CompletableFuture<JobClient>}}
2. submit job succeed -> {{JobClient}}
3. request job result -> {{CompletableFuture<JobExecutionResult>}}
4. get job result -> {{JobExecutionResult}}
However, I notice that {{Executor#execute}} directly returns a final job result
in its test set. I think it is somewhat out of alignment: where will the
difference between these stages stay?
was (Author: tison):
In previous discussion we separate the stage into
1. submit job
2. submit job succeed
3. request job result
4. get job result
However, I notice that {{Executor#execute}} directly returns a final job result
in its test set. I think it is somewhat out of alignment: where will the
difference between these stages stay?
> Add executeAsync() method to 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)
