qianlan717 opened a new pull request, #59977:
URL: https://github.com/apache/spark/pull/59977

   ### What changes were proposed in this pull request?
   
   Read `spark.jars.ivySettings` from the owning SparkSession configuration 
when resolving Maven artifacts for `SparkSession.addArtifact` and 
`addArtifacts`. Use the existing config entry and Spark config provider to 
preserve variable substitution and typed config reading.
   
   ### Why are the changes needed?
   
   Artifact addition is a session-level API, so dependency resolution should 
honor the session's effective Ivy settings. The current SparkContext lookup 
ignores session-specific settings. Cluster-configured settings remain available 
through session configuration inheritance.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. Maven artifact resolution honors session-specific Ivy settings instead 
of always using the SparkContext value. Existing cluster-configured repository 
support is preserved.
   
   ### How was this patch tested?
   
   Extended `ArtifactManagerIvySettingsSuite` to cover inherited settings with 
variable substitution and a session override that resolves a dependency from a 
separate local Maven repository. Existing coverage exercises `addArtifact`, 
`addArtifacts`, session-local caches, timeouts, and cloned sessions.
   
   Verification in progress:
   
   ```text
   build/sbt 'sql/testOnly 
org.apache.spark.sql.artifact.ArtifactManagerIvySettingsSuite'
   ```
   
   `git diff --check` and source line-length and ASCII checks passed.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex (GPT-6)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to