You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2025/03/26 12:28:00 UTC

[jira] [Created] (FLINK-37564) Rework job error fetching to use Exception history instead of JobResults

Gyula Fora created FLINK-37564:
----------------------------------

             Summary: Rework job error fetching to use Exception history instead of JobResults
                 Key: FLINK-37564
                 URL: https://issues.apache.org/jira/browse/FLINK-37564
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
            Reporter: Gyula Fora
            Assignee: Rodrigo Meneses


Currently the Flink operator uses the jobResults to fetch the exceptions but that has a severe limitation that it returns the serialized exception which in most cases cannot be deserialized by the operator.

Instead we should replace this logic using the exception history JM endpoint which returns string based exception info / stack traces



--
This message was sent by Atlassian Jira
(v8.20.10#820010)