[jira] [Closed] (FLINK-15129) Return JobClient instead of JobClient Future from executeAsync()

["Aljoscha Krettek (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek closed FLINK-15129.
------------------------------------
    Fix Version/s: 1.10.0
         Assignee: Aljoscha Krettek
       Resolution: Fixed

Implemented on master in 166e10ff870721230e4316f341da3264b329a8d9
Implemented on release-1.10 in 343daba7f0a8ddb9f1cb6967c586a9ab164163b4

> Return JobClient instead of JobClient Future from executeAsync()
> ----------------------------------------------------------------
>
>                 Key: FLINK-15129
>                 URL: https://issues.apache.org/jira/browse/FLINK-15129
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataSet, API / DataStream
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>             Fix For: 1.10.0
>
>
> Currently, users have to write this when they want to use the {{JobClient}}:
> {code}
> CompletableFuture<JobClient> jobClientFuture = env.executeAsync();
> JobClient jobClient = jobClientFuture.get();
> // or use thenApply/thenCompose etc.
> {code}
> instead we could always return a {{JobClient}} right away and therefore remove one step for the user.
> I don't know if it's always the right choice, but currently we always return an already completed future that contains the {{JobClient}}. In the future we might want to return a future that actually completes at some later point, we would not be able to do this if we directly return a {{JobClient}} and would have to block in {{executeAsync()}}.



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