[jira] [Commented] (FLINK-15116) Make JobClient stateless, remove AutoCloseable

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann commented on FLINK-15116:
---------------------------------------

I think this sub task caused a regression since we no longer set the {{ExecutionEnvironment.lastJobExecutionResult}} field when using the {{ContextEnvironment}}. A user reported this problem when using Gelly [1].

cc [~tison], [~kkl0u]

[1] https://lists.apache.org/thread.html/rfed34be1651aa15fbdd0b3cac0d5607fa34886c1cf1aacf06684e995%40%3Cdev.flink.apache.org%3E

> Make JobClient stateless, remove AutoCloseable
> ----------------------------------------------
>
>                 Key: FLINK-15116
>                 URL: https://issues.apache.org/jira/browse/FLINK-15116
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataSet, API / DataStream
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, {{JobClient}} is {{AutoCloseable}} and we require users to close the {{JobClient}} that they get as a result from {{executeAsync()}}. This is problematic because users can simply ignore the result of {{executeAsync()}} and then we will leak the resources that the client has.
> We should change the {{JobClient}} so that it acquires the required {{ClusterClient}} for each method call and closes it again. 
> This means that the users no longer have the burden of managing the JobClient lifecycle, i.e. they can freely ignore the result of executeAsync().



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