Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-59771521
So one issue is that the scheme was added to properly handle when yarn
using https (SPARK-3286). If client mode isn't passing the scheme then that is
probably broken. If it was passing the scheme that you wouldn't hit this
issue. I think changing the YarnClientSchedulerBackend.start routine where it
sets the spark.driver.appUIAddress would be the equivalent change. And then we
would need to test.
With the above change it would have the scheme included and wouldn't hit
the null. If we want to add the check in anyway for handling the case where it
is null just in case something else comes up, thats fine, but I'm not real fond
of pattern matching here. How about just checking the URI.getScheme and if
null we pass it in as is, otherwise we do the getAuthority()?
---
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]
