xinzhuxiansheng opened a new issue, #4221:
URL: https://github.com/apache/streampark/issues/4221

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/streampark/issues?q=is%3Aissue+label%3A%22improvement%22)
 and found no similar issues.
   
   
   ### Java Version
   
   jdk 1.8
   
   ### Scala Version
   
   2.12.x
   
   ### StreamPark Version
   
   2.1.5
   
   ### Flink Version
   
   flink 1.15.3
   
   ### Deploy mode
   
   kubernetes-application
   
   ### What happened
   
   After the job is started, with the start of flink jm and tm, the status is 
programmed as running. In the job of the finite data source, when the job 
stops, the job status is expected to be FINISHED. However, after running in 
streampark, the final status is FAILED.
   
   作业启动后,随着flink jm,tm启动后,状态编程 running,再有限数据源的job 中,当作业停止时,作业状态期望是 FINISHED, 
可在streampark 运行后,最终的状态是 FAILED
   
   ### Error Exception
   
   ```log
   There is no exception information because Scala uses Try{}.getOrElse(xxxx). 
When an exception occurs, the return value of the method will return the 
default value in ELSE. The method involved in this issue is 
FlinkHistoryArchives#getJobStateFromArchiveFile()
   
   无异常信息,因为Scala 使用的是  Try{}.getOrElse(xxxx) ,当发生异常后,方法的返回值会返回 ELSE里面的默认值,在该 
issue 中 涉及到的方法是 FlinkHistoryArchives#getJobStateFromArchiveFile()
   
   The job status is very important to us. Even if it is abnormal, we would 
like to see an error message.
   
   作业状态对我们来说非常重要,即使异常,我们更希望看到报错
   ```
   
   ### Screenshots
   
   
![Image](https://github.com/user-attachments/assets/f3912efd-02b8-4dac-ac99-a879f76a42ac)
   
   
![Image](https://github.com/user-attachments/assets/b2caf198-41f6-493b-9c28-d1a5ac6653b7)
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?)
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to