You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Pengfei Xu (Jira)" <ji...@apache.org> on 2024/10/22 15:34:00 UTC

[jira] [Updated] (SPARK-50074) ArtifactManager follow-up: better/Lighter registration logic during cloning ArtifactManager

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

Pengfei Xu updated SPARK-50074:
-------------------------------
    Summary: ArtifactManager follow-up: better/Lighter registration logic during cloning ArtifactManager  (was: Better/Lighter registration logic during cloning ArtifactManager)

> ArtifactManager follow-up: better/Lighter registration logic during cloning ArtifactManager
> -------------------------------------------------------------------------------------------
>
>                 Key: SPARK-50074
>                 URL: https://issues.apache.org/jira/browse/SPARK-50074
>             Project: Spark
>          Issue Type: Improvement
>          Components: Connect, SQL
>    Affects Versions: 4.0.0
>            Reporter: Pengfei Xu
>            Priority: Major
>
> In https://github.com/apache/spark/pull/48320 the `ArtifactManager.clone` method, we re-register all existing artifacts with new Session UUID to the new SparkContext. This current logic is a bit heavy and unnecessary because all artifacts are already in place and have passed all necessary checks.
> Ideally, we want to modify the SparkContext.addedJars map directly to insert these artifacts with new session UUIDs - or something that is lightweight.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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