[FLINK-29794] Flink Operator Need to Include Cause for Exceptions If Possible

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.3.0
• Fix Version/s: kubernetes-operator-1.3.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Zhou Jiang
• Reporter: Zhou Jiang
• Created: 28/Oct/22 21:01
• Updated: 13/Dec/22 01:39
• Resolved: 01/Nov/22 09:50

Description

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.

Issue Links

• links to: GitHub Pull Request #422