Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/5294#issuecomment-88183017
So we had run into an issue where something in hadoop changed that required
me to recompile Spark, whereas if it hadn't included the stuff from hadoop in
my classpath it should have worked because the spark assembly jar already
included hadoop. Looks like I unfortunately didn't put the details in the
jira, but I filed this so that you could potentially package Spark and any
confs you needed and be completely independent of what is on the cluster. This
would allow minor incompatibilities/changes between whats on the Hadoop cluster
and the hadoop version Spark was compiled with.
Thinking now I think it had to do with a conf changed in hadoop which
required a new class but it wasn't in the spark assembly. If we hadn't
included the hadoop/yarn stuff in the classpath it would have worked as it
wouldn't have picked up said conf. This is basically the opposite packaging
mechanism then the hadoop provided option.
---
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]
