Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200644697
As I've said above, spark does *not* use the Hadoop configuration from the
classpath in the executors. It uses the hadoop configuration broadcast from the
driver.
So no matter what you add to the executor's classpath, it *will not* be
used.
And in any case, using the configuration present in the submitting node is
more correct than using whatever configuration might or might not be available
on the cluster nodes, which was the whole point of uploading the configuration
archive to the AM in the first place.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]