Github user jerryshao commented on the issue:

    https://github.com/apache/spark/pull/15134
  
    @phalodi we don't restrict user to have to set an app name either for 
SparkContext or SparkSession. You could refer to this code in SparkSubmit:
    
    ```
        // Set name from main class if not given
        name = Option(name).orElse(Option(mainClass)).orNull
        if (name == null && primaryResource != null) {
          name = Utils.stripDirectory(primaryResource)
        }
    ```
    
    Spark will figure out a proper name if user doesn't define one. This 
behavior is consistent both for SparkSession and SparkContext. What we're 
saying is that in most of the cases Spark can figure out a proper name, so the 
code path of UUID may not be touched at all, bother here and SparkSession.
    
    This may be happened only if user bypass SparkSubmit or SparkLauncher. But 
I'm guessing such use cases may not be so many.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to