007a733434
Various spark scripts load spark-env.sh. This can cause growth of any variables that may be appended to (SPARK_CLASSPATH, SPARK_REPL_OPTS) and it makes the precedence order for options specified in spark-env.sh less clear. One use-case for the latter is that we want to set options from the command-line of spark-shell, but these options will be overridden by subsequent loading of spark-env.sh. If we were to load the spark-env.sh first and then set our command-line options, we could guarantee correct precedence order. Note that we use SPARK_CONF_DIR if available to support the sbin/ scripts, which always set this variable from sbin/spark-config.sh. Otherwise, we default to the ../conf/ as usual. Author: Aaron Davidson <aaron@databricks.com> Closes #184 from aarondav/idem and squashes the following commits: e291f91 [Aaron Davidson] Use "private" variables in load-spark-env.sh 8da8360 [Aaron Davidson] Add .sh extension to load-spark-env.sh 93a2471 [Aaron Davidson] SPARK-1286: Make usage of spark-env.sh idempotent |
||
|---|---|---|
| .. | ||
| compute-classpath.cmd | ||
| compute-classpath.sh | ||
| load-spark-env.sh | ||
| pyspark | ||
| pyspark.cmd | ||
| pyspark2.cmd | ||
| run-example | ||
| run-example.cmd | ||
| run-example2.cmd | ||
| spark-class | ||
| spark-class.cmd | ||
| spark-class2.cmd | ||
| spark-shell | ||
| spark-shell.cmd | ||