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

Posted to issues@flink.apache.org by "Xuannan Su (Jira)" <ji...@apache.org> on 2024/04/12 03:38:00 UTC

[jira] [Updated] (FLINK-35089) Two input AbstractStreamOperator may throw NPE when receiving RecordAttributes

     [ https://issues.apache.org/jira/browse/FLINK-35089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xuannan Su updated FLINK-35089:
-------------------------------
    Description: 
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 propose to make the RecordAttributes serializable and these fields non-transient.

 

  was:
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 propose to make the RecordAttributes serialization and these fields non-transient.

 


> 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
>            Priority: Major
>
> 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 propose to make the RecordAttributes serializable and these fields non-transient.
>  



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