Github user KevinGrealish commented on the issue:
https://github.com/apache/spark/pull/13824
@Vanzin I looked at refactoring the client to be more amenable to more
granular unit testing, including using the mockable env var on conf you
mentioned, but concluded it would be too disruptive to be part of this simple
bug fix. I have included a test (that found an issue) and believe this should
be good to go now. I'm not sure why the spark.yarn.appMasterEnv was do java
path style appending, but that appears to be simply incorrect and was changed
to a plain set.
---
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]
