prashantwason opened a new pull request #1289: [HUDI-92] Provide reasonable names for Spark DAG stages in Hudi. URL: https://github.com/apache/incubator-hudi/pull/1289 ## What is the purpose of the pull request HUDI DAG stages do not have any names. The Spark History Server UI shows these stages with the HUDI JAVA filename and the line number. This change provides descriptive names for the stages which makes it easier to visualize the HUDI DAG. ## Brief change log 1. All code locations where JavaSparkContext.XXX (DAG creation methods like parallelize) are used have been updated with descriptive names for the job with the following API jsc.setJobGroup(title, description); 2. Title is the class name so its easy to identify. Description is the activity for that stage. 3. Unit test code has been updates to enable the unit tests to write the Spark event logs so that even the unit tests can be visualized in a locally installed Spark History Server UI. 4. The unit tests need to be run as follows: mvn test -DSPARK_EVLOG_DIR=/path/for/spark/event/log Once the unit tests complete, the Spark History Server shows the application logs for all completed unit tests. The unit tests themselves can be identified by the test-class-name as the application name. ## Verify this pull request -- This pull request is already covered by existing tests, such as *(please describe tests)*. 1. All existing unit tests pass. 2. If the SPARK_EVLOG_DIR property is not set, spark event logging is not enabled (this is defauly behavior) 3. Manually verified the change by running unit tests locally and observing the application logs on the locally installed Spark History Server. ## Committer checklist - [ ] Has a corresponding JIRA in PR title & commit - [ ] Commit message is descriptive of the change - [ ] CI is green - [ ] Necessary doc changes done or have another open PR - [ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
