Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-38533060
So when we extend a classloader and provide the parent the loadClass
function will resolve through the parent rather than the child which is why we
avoid it for the Child case and use it in the parent case.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---