Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/2795
Merging ...
---
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
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/2795
Rebased and pushed to travis again:
https://travis-ci.org/rmetzger/flink/builds/178664750
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2795
+1
---
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
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2795
Rebased this on latest release branch and going to merge later today after
Travis.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2795
That's completely reasonable. For 1.2, should we change the way
`getRuntimeContext().getUserCodeClassLoader()` works for per-job Yarn clusters?
Should it return the system class loader there?
---
If
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2795
I also was very torn when it came to this change.
In the end, I lean towards keeping user behavior in 1.1.4 consistent. The
fix is in 1.2, which is not too far away, and there it is
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2795
Thanks. +1 for reverting then!
---
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
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()
```
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2795
Thanks for the PR @uce! Could you explain how the user would retrieve the
user class loader to load classes during runtime? Is the user class loader
exposed to the user?
---
If your project is set up
