Flowfile contents are corrupted after upgrading to NIFI 1.23.1

[#1]

Hi,

I am running NIFI in Kubernetes cluster with 3 nodes. After the upgrade of NIFI to 1.23.1 version, most of the time, the JSON messages or CSV files are corrupted something like below, which is causing serious production issues to my workflows. 

Actual message:

{"RequestPeriod":"morning","TRANSMISSION_TYPE":"","ReturnDatetime":"2022-02-07T13:00:00+01:00", "PickupDatetime":"2022-02-07T08:00:00+01:00"}

Corrupted message:

1:00"}{"RequestPeriod":"morning","TRANSMISSION_TYPE":"","ReturnDatetime":"2022-02-07T13:00:00+01:00", "PickupDatetime":"2022-02-07T08:00:00+0

Additional screenshots:

OUTPUT:

This is become an URGENT issue now. Any support would be highly appreciated.

[#2 · Accepted solution]

@Barsha 

It is possible you may be hitting https://issues.apache.org/jira/browse/NIFI-11971 that affects Apache NiFI 1.23.0 and 1.23.1.  It has been addressed in Apache NiFi 1.23.2, so please upgrade to that latest version:
https://nifi.apache.org/download.html

So you will want to upgrade to Apache NiFi 1.23.2+

This bug fix is already included in the CFM 2.1.6 release and was not a bug in earlier CFM releases:
https://docs.cloudera.com/cfm/2.1.6/release-notes/topics/cfm-fixed-issues.html

If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

[#3 · Accepted solution]

@Barsha 

It is possible you may be hitting https://issues.apache.org/jira/browse/NIFI-11971 that affects Apache NiFI 1.23.0 and 1.23.1.  It has been addressed in Apache NiFi 1.23.2, so please upgrade to that latest version:
https://nifi.apache.org/download.html

So you will want to upgrade to Apache NiFi 1.23.2+

This bug fix is already included in the CFM 2.1.6 release and was not a bug in earlier CFM releases:
https://docs.cloudera.com/cfm/2.1.6/release-notes/topics/cfm-fixed-issues.html

If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

[#4 · Accepted solution]

This indeed solved the problem. Thanks a lot for your support.