GitHub user BryanCutler opened a pull request:
https://github.com/apache/spark/pull/13428
[SPARK-12666][CORE] SparkSubmit packages fix for when 'default' conf
doesn't exist in dependent module
## What changes were proposed in this pull request?
Adding a "(*)" to the dependency configuration will set a fallback to any
configuration present, if the conf set is not found. E.g. with the setting
"default(*)", Ivy will look for the conf "default" in the module and if not
found will use the first conf it finds in the module. This can help with the
case when using "sbt publishLocal" which does not write a "default" conf in the
published ivy.xml file.
## How was this patch tested?
used spark-submit with --packages option for a package published locally
with no default conf, and a package resolved from Maven central.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BryanCutler/spark
fallback-package-conf-SPARK-12666
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13428.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13428
----
commit 27d0c210dcaa72613f1042aa2406d22fc1e5cf7a
Author: Bryan Cutler <cutl...@gmail.com>
Date: 2016-06-01T00:24:37Z
Added fallback wildcard for the case where 'default' conf doesn't exist
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
