Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/539#issuecomment-41416489
Well, the current patch does not work correctly because with it
SPARK_YARN_APP_NAME becomes useless.
But before the patch my app name (set using the conf, not
SPARK_YARN_APP_NAME) was never set in yarn, it was always "Spark". To set my
app name in Yarn that way I'd have to use "-Dspark.app.name" in the JVM
options, and not SparkConf.setAppName().
So the discussion is whether to keep SPARK_YARN_APP_NAME or get rid of it;
since both are user-provided, I don't see a reason for keeping both, unless
there's some other benefit that I'm not seeing.
---
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.
---
