Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46324012
Sorry if I wan't clear. I didn't mean to update ClientArguments with that
logic, I just meant that is the logic we want overall. We don't want to
duplicate code if possible.
Overall I think if the --files/--archives are specified to ClientArguments
we don't touch them. If they aren't specified we look at the config variables
and resolveURI them. Then we need to modify the YarnClientSchedulerBackend to
properly handle when spark.yarn.dist.archives/spark.yarn.dist.files configs are
set (but not set by spark-submit script) (it should default to file://, not
hdfs://).
---
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.
---
