4paradigm / 4paradigm/OpenMLDB
Change Spark status to avoid getting FINISHED before getting FAILED
Ouverte
enhancement
- Langage dominant
- C++
- Étoiles
- 1.7k
- Forks
- 331
- Merge moyen
- 12 j 12 h
- PR mergées (30 j)
- 1
Description
Now it is confusing when job status change FINISHED to FAILED.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- spark
- Domaine
- backend, databases, machine-learning
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100