You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Zhan Zhang (JIRA)" <ji...@apache.org> on 2014/11/17 23:49:33 UTC
[jira] [Updated] (SPARK-4461) Spark should not relies on
mapred-site.xml for classpath
[ https://issues.apache.org/jira/browse/SPARK-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhan Zhang updated SPARK-4461:
------------------------------
Description:
Currently spark read mapred-site.xml to get the class path. From hadoop 2.6, the library is shipped to cluster with distributed cache at run-time, and may not be available at every node manager.
Instead of relying on mapred-site.xml, spark should handle this by its own, for example, through ADD_JARs, SPARK_CLASSPATH, etc
was:
Currently spark read mapred-site.xml to get the class path. From hadoop 2.6, the library is shipped to cluster with distributed cache at run-time, and may not be available at every node manager.
Instead of relying on mapred-site.xml, spark should handle this by its own, for example, through ADD_JARs.
> Spark should not relies on mapred-site.xml for classpath
> --------------------------------------------------------
>
> Key: SPARK-4461
> URL: https://issues.apache.org/jira/browse/SPARK-4461
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Reporter: Zhan Zhang
>
> Currently spark read mapred-site.xml to get the class path. From hadoop 2.6, the library is shipped to cluster with distributed cache at run-time, and may not be available at every node manager.
> Instead of relying on mapred-site.xml, spark should handle this by its own, for example, through ADD_JARs, SPARK_CLASSPATH, etc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org