spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-21798) No config to replace deprecated SPARK_CLASSPATH config for launching daemons like History Server
Date Mon, 28 Aug 2017 13:52:01 GMT

     [ https://issues.apache.org/jira/browse/SPARK-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Graves updated SPARK-21798:
----------------------------------
    Issue Type: Bug  (was: Improvement)

> No config to replace deprecated SPARK_CLASSPATH config for launching daemons like History
Server
> ------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-21798
>                 URL: https://issues.apache.org/jira/browse/SPARK-21798
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.2.0
>            Reporter: Sanket Reddy
>            Priority: Minor
>
> History Server Launch uses SparkClassCommandBuilder for launching the server. It is observed
that SPARK_CLASSPATH has been removed and deprecated. For spark-submit this takes a different
route and spark.driver.extraClasspath takes care of specifying additional jars in the classpath
that were previously specified in the SPARK_CLASSPATH. Right now the only way specify the
additional jars for launching daemons such as history server is using SPARK_DIST_CLASSPATH
(https://spark.apache.org/docs/latest/hadoop-provided.html) but this I presume is a distribution
classpath. It would be nice to have a similar config like spark.driver.extraClasspath for
launching daemons similar to history server. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message