You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Sander Bylemans (Jira)" <ji...@apache.org> on 2024/06/05 11:05:00 UTC
[jira] [Updated] (NIFI-13362) JSONRecordSetWriter does not account for schema changes when writing serialized form
[ https://issues.apache.org/jira/browse/NIFI-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sander Bylemans updated NIFI-13362:
-----------------------------------
Affects Version/s: 2.0.0-M3
> JSONRecordSetWriter does not account for schema changes when writing serialized form
> ------------------------------------------------------------------------------------
>
> Key: NIFI-13362
> URL: https://issues.apache.org/jira/browse/NIFI-13362
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.26.0, 2.0.0-M3
> Reporter: Sander Bylemans
> Priority: Critical
>
> When using the RemoveRecordField processor with the JsonRecordSetWriter as a writer, I came across an issue where not all fields were removed in the resulting records.
> When debugging, I noticed the JsonRecordSetWriter uses the WriteJsonResult, which checks if there is a serialized form of the record. If there is, it just uses that even though the serialized form may contain fields that are not present anymore.
> There is a check on the schema of the record, if it is the same as the target schema, but the serialized form does not account for this schema change introduced by the RemoveRecordField processor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)