[
https://issues.apache.org/jira/browse/FLINK-34957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Fan updated FLINK-34957:
----------------------------
Description:
JDBC Autoscaler event handler doesn't allow the event message is null, but the
message may be null when we handle the exception.
We consider the exception message as the event message, but the exception
message may be null, such as: TimeoutException. (It has been shown in following
picture.)
Also, recording a event without any message is meaningless. It doesn't have any
benefit for troubleshooting.
Solution:
* Consider the exception message as the event message when exception message
isn't null
* The whole Exception as the event message if exception message is null.
!image-2024-03-28-11-57-35-234.png!
was:
JDBC Autoscaler event handler doesn't allow the event message is null, but the
message may be null when we handle the exception.
We consider the exception message as the event message, but the exception
message may be null, such as: TimeoutException. (It has been shown in following
picture.)
Also, ecording a event without any message is meaningless. It doesn't have any
benefit for troubleshooting.
Solution:
* Consider the exception message as the event message when exception message
isn't null
* The whole Exception as the event message if exception message is null.
!image-2024-03-28-11-57-35-234.png!
> JDBC Autoscaler event handler throws Column 'message' cannot be null
> ---------------------------------------------------------------------
>
> Key: FLINK-34957
> URL: https://issues.apache.org/jira/browse/FLINK-34957
> Project: Flink
> Issue Type: Bug
> Components: Autoscaler
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.9.0
>
> Attachments: image-2024-03-28-11-57-35-234.png
>
>
> JDBC Autoscaler event handler doesn't allow the event message is null, but
> the message may be null when we handle the exception.
> We consider the exception message as the event message, but the exception
> message may be null, such as: TimeoutException. (It has been shown in
> following picture.)
> Also, recording a event without any message is meaningless. It doesn't have
> any benefit for troubleshooting.
> Solution:
> * Consider the exception message as the event message when exception message
> isn't null
> * The whole Exception as the event message if exception message is null.
> !image-2024-03-28-11-57-35-234.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
