You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Gyorgy Gal (Jira)" <ji...@apache.org> on 2025/11/10 17:14:01 UTC
[jira] [Updated] (LIVY-152) Livy should use PYSPARK_ARCHIVES_PATH instead of having its own setting
[ https://issues.apache.org/jira/browse/LIVY-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyorgy Gal updated LIVY-152:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If you feel this is moved out inappropriately, feel free to provide justification and reset the Fix Version to 0.9.0.
> Livy should use PYSPARK_ARCHIVES_PATH instead of having its own setting
> -----------------------------------------------------------------------
>
> Key: LIVY-152
> URL: https://issues.apache.org/jira/browse/LIVY-152
> Project: Livy
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.2
> Reporter: Marcelo Masiero Vanzin
> Priority: Major
> Fix For: 0.10.0
>
>
> Spark uses {{PYSPARK_ARCHIVES_PATH}} to override the default location of the python archives, so that they can be cached in HDFS for example.
> Livy currently has its own setting for that, but it would be nice to use Spark's configuration when possible.
> Note that when LIVY-106 is implemented, this will become harder (since that's an env variable and not a setting in spark-defaults.conf). But right now we could just source {{spark-env.sh}} when starting Livy to get it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)