Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8959#issuecomment-145125393
Hmm, I think I see what you mean. Maybe there should be separate handling
for app jar vs. other jars when `spark.yarn.user.classpath.first` is set.
May this code is overdue for a cleanup / sanity check...
If it starts to get too nasty it might just be easier to add `APP_JAR` to
the classpath like you're doing, and hope the bug doesn't affect anything else.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
