DanielLeens commented on issue #10039: URL: https://github.com/apache/seatunnel/issues/10039#issuecomment-4861294149
Thanks for reporting this with the storage configuration included. This does look like a server-side issue in the finished-job REST path rather than a basic usage problem. The important clue is that `./bin/seatunnel.sh --list` still works while the web `/finished-jobs` path fails, which means the failure is likely in the REST/UI-specific history materialization path rather than in the underlying job-history data existing at all. I checked the current code path, and `/finished-jobs` loads all finished job records and sorts them before building the response. That path is less defensive than the CLI path, so one plausible failure mode is that a persisted historical entry restored from the map store is missing a field such as `finishTime`, or another finished-job record is only partially available, and the REST path ends up hitting a null-sensitive operation. To pin down the exact failing field, we still need one thing from the server side: 1. the full `NullPointerException` stack trace from `seatunnel-engine-master.log` for one failing `/finished-jobs` request That stack trace will tell us whether the null is coming from sorting, history record conversion, or one of the finished-job companion stores. Once we have that, we can narrow the fix much more precisely. For now, the CLI listing is the best temporary workaround, since it is clearly going through a different and currently more tolerant path. -- 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]
