You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/01/14 20:29:39 UTC
[jira] [Created] (FLINK-3236) Flink user code classloader should
have Flink classloader as parent classloader
Stephan Ewen created FLINK-3236:
-----------------------------------
Summary: 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
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)