Aljoscha Krettek created FLINK-15129: ----------------------------------------
Summary: 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 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)