Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
From: sryza <git@git.apache.org>
To: dev@spark.apache.org
Reply-To: dev@spark.apache.org
References: <git-pr-102-spark@git.apache.org>
In-Reply-To: <git-pr-102-spark@git.apache.org>
Subject: [GitHub] spark pull request: SPARK-1064
Content-Type: text/plain
Message-Id: <20140311013921.8CC5693E1B6@tyr.zones.apache.org>
Date: Tue, 11 Mar 2014 01:39:21 +0000 (UTC)

Github user sryza commented on a diff in the pull request:

    https://github.com/apache/spark/pull/102#discussion_r10458903
  
    --- Diff: yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
    @@ -379,7 +381,17 @@ object ClientBase {
     
       // Based on code from org.apache.hadoop.mapreduce.v2.util.MRApps
       def populateHadoopClasspath(conf: Configuration, env: HashMap[String, String]) {
    -    for (c <- conf.getStrings(YarnConfiguration.YARN_APPLICATION_CLASSPATH)) {
    +    val classpathEntries = Option(conf.getStrings(
    --- End diff --
    
    It points to the location on machines in the cluster of the HDFS/YARN/MR code. An admin might add a library like LZO to this, but users should instead be using the distributed cache if there's a jar specific to their application that they want.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---