[jira] [Commented] (NIFI-6925) JoltTransformRecord, PutESHttpRecord, PutHive3Streaming fail with various RecordReaders

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998383#comment-16998383 ] 

ASF subversion and git services commented on NIFI-6925:
-------------------------------------------------------

Commit 6d1bcc22e78129b2669c2e41af0c6b246e6780a9 in nifi's branch refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6d1bcc2 ]

NIFI-6925: Fixed JoltTransformRecord for RecordReaders, improved MockProcessSession (#3913)

* NIFI-6925: Fixed JoltTransformRecord for RecordReaders, improved MockProcessSession

* Fixed logic for no records, added unit test

* Fixed PutElasticsearchHttpRecord and PutHive3Streaming, same bug as JoltTransformRecord

* Added null checks


> JoltTransformRecord, PutESHttpRecord, PutHive3Streaming fail with various RecordReaders
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-6925
>                 URL: https://issues.apache.org/jira/browse/NIFI-6925
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When using JoltTransformRecord with readers such as AvroReader or CSVReader, an error occurs when trying to transfer the original input flowfile to the "original" relationship. The error indicates that it is reading from multiple callbacks or that the input stream is still open. It happens to work with JsonTreeReader because the underlying JSON parser closes the stream when no more records are available.
> This is a result of not explicitly closing the input stream before trying to transfer the input flow file. It was not caught in the unit tests because MockProcessSession doesn't keep track of the open reader count, so that should be fixed as well. Fixing MockProcessSession will cause TestJoltTransformRecord to fail before the fix for this case is applied.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)