[
https://issues.apache.org/jira/browse/FLINK-14916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kostas Kloudas closed FLINK-14916.
----------------------------------
Resolution: Fixed
For a clean Jira I will close this until the discussion in
https://issues.apache.org/jira/browse/FLINK-15129 is resolved. With the
discussion there, I tend to believe that maybe returning a {{JobClient}} rather
than a {{Future}} with a {{JobClient}} is more consistent with the expected
semantics, as it does not make sense to return a {{JobClient}} for a job that
is not _successfully_ submitted.
If we still think that this should be implemented, then i will reopen the issue.
> Asynchronously deploy cluster in AbstractJobClusterExecutor#execute
> -------------------------------------------------------------------
>
> Key: FLINK-14916
> URL: https://issues.apache.org/jira/browse/FLINK-14916
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Affects Versions: 1.10.0
> Reporter: Zili Chen
> Assignee: Kostas Kloudas
> Priority: Major
>
> https://github.com/apache/flink/pull/10251#discussion_r348933298
> since {{execute}} returns {{CompletableFuture<JobClient>}} we'd better run
> deployment action asynchronously.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
