spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Resolved] (SPARK-4831) Current directory always on classpath with spark-submit
Date Sat, 24 Jan 2015 23:09:34 GMT


Sean Owen resolved SPARK-4831.
       Resolution: Fixed
    Fix Version/s: 1.3.0
         Assignee: Daniel Darabos

Looks like this was merged in

> Current directory always on classpath with spark-submit
> -------------------------------------------------------
>                 Key: SPARK-4831
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy
>    Affects Versions: 1.1.1, 1.2.0
>            Reporter: Daniel Darabos
>            Assignee: Daniel Darabos
>            Priority: Minor
>             Fix For: 1.3.0
> 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 [|]:
> {code}
> {code}
> 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!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message