GitHub user BryanCutler opened a pull request:

    [SPARK-17568][CORE][DEPLOY] Add spark-submit option to override ivy 
settings used to resolve packages/artifacts

    ## What changes were proposed in this pull request?
    Adding option in spark-submit to allow overriding the default IvySettings 
used to resolve artifacts as part of the Spark Packages functionality.  This 
will allow all artifact resolution to go through a central managed repository, 
such as Nexus or Artifactory, where site admins can better approve and control 
what is used with Spark apps.
    This change restructures the creation of the IvySettings object in two 
distinct ways.  First, if the `spark.ivy.settings` option is not defined then 
`buildIvySettings` will create a default settings instance, as before, with 
defined repositories (Maven Central) included.  Second, if the option is 
defined, the ivy settings file will be loaded from the given path and only 
repositories defined within will be used for artifact resolution.
    ## How was this patch tested?
    Existing tests for default behaviour, Manual tests that load a 
ivysettings.xml file with local and Nexus repositories defined.

You can merge this pull request into a Git repository by running:

    $ git pull spark-custom-IvySettings

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15119
commit cc1ad11359567adafb6336db447620cfe046f359
Author: Bryan Cutler <>
Date:   2016-05-11T23:51:27Z

    added option to load IvySettings from file instead of hard-coded settings

commit 97ea3a4a072bbfcb1ece774df4fb7aa7d8c8c551
Author: Bryan Cutler <>
Date:   2016-05-12T17:54:39Z

    added parenthesis to be consistent

commit 1f472ff9962c5b59eaa6e287afcb421f886fc83b
Author: Bryan Cutler <>
Date:   2016-09-16T16:38:52Z

    Merge remote-tracking branch 'upstream/master' into 


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to