4paradigm / 4paradigm/OpenMLDB
Change Spark status to avoid getting FINISHED before getting FAILED
Open
enhancement
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
Now it is confusing when job status change FINISHED to FAILED.
Contributor guide
Research direction
Look for Spark job status handling in the codebase, likely in modules related to job scheduling or Spark integration. The issue mentions avoiding 'FINISHED' before 'FAILED', so examine state transition logic. Check for existing tests around job status to understand the current behavior and where changes are needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spark
- Domain
- backend, databases, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100