[
https://issues.apache.org/jira/browse/FLINK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666468#comment-15666468
]
ASF GitHub Bot commented on FLINK-4913:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2795
Hey Max! I was also not aware of this issue but Stephan pointed it out to
me. You can access the user code loader in rich functions via
```
getRuntimeContext().getUserCodeClassLoader()
```
I think it's very good that we changed it for 1.2, but just to make sure
that there are no surprises (although unlikely) for users upgrading within the
1.1 series.
> Per-job Yarn clusters: include user jar in system class loader
> ---------------------------------------------------------------
>
> Key: FLINK-4913
> URL: https://issues.apache.org/jira/browse/FLINK-4913
> Project: Flink
> Issue Type: Improvement
> Components: Client, YARN Client
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.2.0, 1.1.4
>
>
> Including the jar directly in the system classloader avoids loading it for
> every instantiation of the ExecutionGraph and every Task execution. Note,
> this is only possible for per-job clusters (i.e. Yarn/Mesos).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
