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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
