[SPARK-4831] Current directory always on classpath with spark-submit

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.1, 1.2.0
• Fix Version/s: 1.3.0
• Component/s: Deploy
• Assignee: Daniel Darabos
• Reporter: Daniel Darabos
• Created: 11/Dec/14 15:42
• Updated: 24/Mar/15 10:38
• Resolved: 24/Jan/15 23:09

Description

We had a situation where we were launching an application with spark-submit, and a file (play.plugins) was on the classpath twice, causing problems (trying to register plugins twice). Upon investigating how it got on the classpath twice, we found that it was present in one of our jars, and also in the current working directory. But the one in the current working directory should not be on the classpath. We never asked spark-submit to put the current directory on the classpath.

I think this is caused by a line in compute-classpath.sh:

CLASSPATH="$SPARK_CLASSPATH:$SPARK_SUBMIT_CLASSPATH"

Now if SPARK_CLASSPATH is empty, the empty string is added to the classpath, which means the current working directory.

We tried setting SPARK_CLASSPATH to a bogus value, but that is not allowed.

What is the right solution? Only add SPARK_CLASSPATH if it's non-empty? I can send a pull request for that I think. Thanks!

Issue Links

• is related to: SPARK-6491 Spark will put the current working dir to the CLASSPATH