fix(spark): Add clearJobStatus() calls after setJobStatus() operations #17451
+35
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prashantwason
changed the title
prashantwason
changed the title
yihua
reviewed
Dec 3, 2025
.../hudi-spark-client/src/main/java/org/apache/hudi/client/common/HoodieSparkEngineContext.java
Outdated
Show resolved
Hide resolved
prashantwason
force-pushed
the
pw_oss_commit_porting_2
branch
from
aae6c95 to
43fae98
Compare
prashantwason
changed the title
Contributor
|
hey @prashantwason : can you rebase w/ latest master. |
prashantwason
force-pushed
the
pw_oss_commit_porting_2
branch
from
43fae98 to
b1c04f9
Compare
github-actions
bot
added
size:XL
After a job is completed its status (description shown in UI) should be cleared otherwise any future job which does not set its own job status will end up showing the older job status which is confusing on the UI. Currently, setting and clearing job status is only implemented for Spark which shows the status on SHS UI in the jobs tab.
prashantwason
force-pushed
the
pw_oss_commit_porting_2
branch
from
b1c04f9 to
753f516
Compare
github-actions
bot
added
size:S
yihua
reviewed
Jan 8, 2026
Contributor
yihua
left a comment
yihua
left a comment
There was a problem hiding this comment.
@prashantwason could you check if the PR #9899 is still useful after your change?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the issue this Pull Request addresses
After a job completes, its job group and description continues to show on the Spark history server UI for following jobs which may not be setting their own job status correctly. This causes confusion as stale job descriptions persist in the UI.
Summary and Changelog
Added
clearJobStatus()API toHoodieEngineContextand corresponding calls after parallel operations complete.Changes:
clearJobStatus()method toHoodieEngineContextHoodieSparkEngineContext(clears viajavaSparkContext.setJobDescription(null)),HoodieFlinkEngineContext,HoodieJavaEngineContext, andHoodieLocalEngineContext(no-op)clearJobStatus()calls after parallel operations in:HoodieBloomIndex.java- after range pruningCleanPlanActionExecutor.java- after partition listing and file slice generationBaseSparkCommitActionExecutor.java- after clustering handle, write operations, workload profile, and commitFSUtils.java- after parallel path listingFileSystemBackedTableMetadata.java- after partition and file listingImpact
Enhancement to the Spark History Server UI. Job descriptions will now be properly cleared after operations complete, preventing stale status from appearing on subsequent jobs.
Risk Level
Low. This is a cosmetic change limited to the Spark History Server UI display.
Documentation Update
None required. This is an internal implementation detail that improves UI clarity.
Contributor's checklist