Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/12678#issuecomment-215249127
> If --jars doesn't add it to the classpath then we broke it.
No, that was intentional. jars adds the jars to the application's class
loader (which is different from the JVM's system class path). That's how
standalone and mesos have always behaved, and YARN started behaving like that
since a few releases at least.
If you want app jars to be in the system class path you need to use the
trick described above, or use `spark.yarn.user.classpath.first`.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
