[
https://issues.apache.org/jira/browse/FLINK-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131754#comment-16131754
]
ASF GitHub Bot commented on FLINK-7442:
---------------------------------------
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4554
The system class loader stuff was leftover from an earlier version, I
didn't mean to have that in there.
In the first version I copied the `ChildFirstClassLoader` from
https://github.com/apache/flink/blob/fa11845b926f8371e9cee47775ca0e48176b686e/flink-contrib/flink-statebackend-rocksdb/src/test/java/org/apache/flink/contrib/streaming/state/RocksDbMultiClassLoaderTest.java#L78.
However, when I added the end-to-end tests I noticed that Akka was not working
correctly anymore because it couldn't find some configuration stuff. (I'm
running that again so that I can post the actual error messages)
I also changed the class loader code on the client because I thought people
might be just as likely to use their clashing dependencies there as in
operators. In that case they would suffer from the same problems. We're, after
all, also creating a user-code class loader here. I'm happy to be convinced
otherwise, though.
> Add option for using a child-first classloader for loading user code
> --------------------------------------------------------------------
>
> Key: FLINK-7442
> URL: https://issues.apache.org/jira/browse/FLINK-7442
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
