[FLINK-35089][runtime] Initialize lastRecordAttributes in AbstractStreamOperator during setup

[Sxnan]

What is the purpose of the change

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.

Brief change log

• Initialize the two fields in the setup method.

Verifying this change

This change added tests and can be verified as follows:

• Integration test is added org.apache.flink.test.streaming.runtime.RecordAttributesPropagationITCase

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializer: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 1561a87 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[Sxnan]

@xintongsong Can you help review this PR?

[elvirasru]

Hello,

Could you tell me when the new version with this fix will be released?

Thank you in advance!

PS: I have been facing this issue in version 1.19.0 when trying to connect a HybridSource with another source and process them. This is the error:
Caused by: java.lang.NullPointerException: Cannot invoke "org.apache.flink.streaming.runtime.streamrecord.RecordAttributes.isBacklog()" because "lastAttributes" is null
I am not sure if this BUG was introduced in version 1.19.0, as apparently version 1.18.1 works for me.