Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/15#issuecomment-38709268
I guess I don't understand the first problem. Could you explain it in more
detail? Can you produce a test case where, even if the delegation order is
fixed, there is an error?
As far as I can tell, when an executor is created it will properly set the
delegation order. So in the case where the executor is running inside the same
JVM as the driver, the delegation order will ensure that you can't have
duplicate class definitions in different loaders.
---
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.
---
