Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/3557#issuecomment-69177980
I've tested it and results are:
Before this patch:
Setting|name in client mode|name in cluster mode
---------|-------------------------|---------------------------
none|org.apache.spark.examples.SparkPi|org.apache.spark.examples.SparkPi
spark.app.name|spark.app.name|spark.app.name
SPARK_YARN_APP_NAME|SPARK_YARN_APP_NAME|org.apache.spark.examples.SparkPi
spark.app.name and SPARK_YARN_APP_NAME|SPARK_YARN_APP_NAME|spark.app.name
After this patch:
Setting|name in client mode|name in cluster mode
---------|-------------------------|---------------------------
none|org.apache.spark.examples.SparkPi|org.apache.spark.examples.SparkPi
spark.app.name|spark.app.name|spark.app.name
SPARK_YARN_APP_NAME|org.apache.spark.examples.SparkPi|org.apache.spark.examples.SparkPi
spark.app.name and SPARK_YARN_APP_NAME|spark.app.name|spark.app.name
As @vanzin said, the `SPARK_YARN_APP_NAME` becomes useless since
`spark.app.name` is mandatory.
Note: In test cases I didn't use `SparkConf.setAppName` in application code.
---
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]
