Repository: spark
Updated Branches:
  refs/heads/branch-1.5 84f510c4f -> b6a09331f


[SPARK-10952] Only add hive to classpath if HIVE_HOME is set.

Currently if it isn't set it scans `/lib/*` and adds every dir to the
classpath which makes the env too large and every command called
afterwords fails.

Author: Kevin Cox <[email protected]>

Closes #8994 from kevincox/kevincox-only-add-hive-to-classpath-if-var-is-set.


Project: http://git-wip-us.apache.org/repos/asf/spark/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark/commit/b6a09331
Tree: http://git-wip-us.apache.org/repos/asf/spark/tree/b6a09331
Diff: http://git-wip-us.apache.org/repos/asf/spark/diff/b6a09331

Branch: refs/heads/branch-1.5
Commit: b6a09331fd0411866688960f0039929c08ae87b1
Parents: 84f510c
Author: Kevin Cox <[email protected]>
Authored: Wed Oct 7 09:53:17 2015 -0700
Committer: Josh Rosen <[email protected]>
Committed: Wed Oct 7 09:55:11 2015 -0700

----------------------------------------------------------------------
 build/sbt | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/spark/blob/b6a09331/build/sbt
----------------------------------------------------------------------
diff --git a/build/sbt b/build/sbt
index cc3203d..7d8d099 100755
--- a/build/sbt
+++ b/build/sbt
@@ -20,10 +20,12 @@
 # When creating new tests for Spark SQL Hive, the HADOOP_CLASSPATH must 
contain the hive jars so
 # that we can run Hive to generate the golden answer.  This is not required 
for normal development
 # or testing.
-for i in "$HIVE_HOME"/lib/*
-do HADOOP_CLASSPATH="$HADOOP_CLASSPATH:$i"
-done
-export HADOOP_CLASSPATH
+if [ -n "$HIVE_HOME" ]; then
+    for i in "$HIVE_HOME"/lib/*
+    do HADOOP_CLASSPATH="$HADOOP_CLASSPATH:$i"
+    done
+    export HADOOP_CLASSPATH
+fi
 
 realpath () {
 (


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to