[
https://issues.apache.org/jira/browse/FLINK-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-3236.
---------------------------------
Resolution: Fixed
Fixed in
- 0.10.2 via 2d7f0b1af7f490e6f341ed0b08aa561a67e457b5
- 1.0.0 via 0ae46b596949808f56c40bd7a68f478bc10206ab
> Flink user code classloader should have Flink classloader as parent
> classloader
> -------------------------------------------------------------------------------
>
> Key: FLINK-3236
> URL: https://issues.apache.org/jira/browse/FLINK-3236
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime
> Affects Versions: 0.10.1
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.0.0, 0.10.2
>
>
> Right now, the user code classloader delegates to the system classloader as
> parent. That works in Flink standalone settings, but not when the Flink core
> classes themselves are not loaded with the system classloader (certain
> embedded setups)
> Giving the classloader that was used to load the Flink core classes (like for
> example {{org.apache.flink.runtime.taskmanager.Task.class.getClassLoader()}}
> solves that problem and does not break behavior in standalone mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
