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

Posted to issues@flink.apache.org by "Zhou Jiang (Jira)" <ji...@apache.org> on 2022/10/28 21:02:00 UTC

[jira] [Created] (FLINK-29794) Flink Operator Need to Include Cause for Exceptions If Possible

Zhou Jiang created FLINK-29794:
----------------------------------

             Summary: Flink Operator Need to Include Cause for Exceptions If Possible
                 Key: FLINK-29794
                 URL: https://issues.apache.org/jira/browse/FLINK-29794
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.3.0
            Reporter: Zhou Jiang


For easier debugging and consistent stack trace, it would be appreciated if Exceptions are always thrown with cause (if exists), instead of persisting string message & silently swallow the cause. 

This issue currently present in apache.flink.kubernetes.operator.reconciler.diff.ReflectiveDiffBuilder and apache.flink.kubernetes.operator.utils.EnvUtils

 

We would like to suggest this as a pattern for future exception handling as well.



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