[
https://issues.apache.org/jira/browse/SPARK-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136196#comment-16136196
]
Saisai Shao commented on SPARK-21798:
-------------------------------------
I think this one could be used, looks like there's no other options in the
current code.
BTW, why do you need to expand Spark history server's classpath, do you have
some customized history provider?
> 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: Improvement
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
