[
https://issues.apache.org/jira/browse/FLINK-35089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923900#comment-17923900
]
Yohei Yoshimuta commented on FLINK-35089:
-----------------------------------------
FYI: We encountered this issue when upgrading Flink-CDC (MySQL connector) from
3.0.1 to 3.3.0 while using Flink 1.19.0. However, upgrading to 3.1.1 or 3.2.1
did not cause this problem.
At first, I wasn’t sure if upgrading Flink-CDC was related to this fix, but
upgrading Flink to 1.19.1 resolved the issue. I just wanted to share my
troubleshooting experience for users who may face the same issue in the near
future.
> Two input AbstractStreamOperator may throw NPE when receiving RecordAttributes
> ------------------------------------------------------------------------------
>
> Key: FLINK-35089
> URL: https://issues.apache.org/jira/browse/FLINK-35089
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.19.0
> Reporter: Xuannan Su
> Assignee: Xuannan Su
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0, 1.19.1
>
>
> Currently the `lastRecordAttributes1` and `lastRecordAttributes2` in the
> `AbstractStreamOperator` are transient. The two fields will be null when it
> is deserialized in TaskManager, which may cause an NPE.
> To fix it, we will initialize the two fields in the {{setup}} method.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
