You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/09/02 11:05:00 UTC

[jira] [Commented] (FLINK-19124) Some JobClient methods are not ergonomic, require ClassLoader argument

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

Aljoscha Krettek commented on FLINK-19124:
------------------------------------------

I'd be very happy to work in this with a contributor if someone is interested.

> Some JobClient methods are not ergonomic, require ClassLoader argument
> ----------------------------------------------------------------------
>
>                 Key: FLINK-19124
>                 URL: https://issues.apache.org/jira/browse/FLINK-19124
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Aljoscha Krettek
>            Priority: Major
>              Labels: starter
>
> Both {{getAccumulators()}} and {{getJobExecutionResult()}} result require the user to give a {{ClassLoader}}. In a lot of cases the {{JobClient}} is created in a context where we already know the user-code {{ClassLoader}}. We should see whether we can remove the class loader from those methods. This might require that users give a class loader when constructing a {{JobClient}} themselves for an already running job but the trade-off seems to be worth it.



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