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

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

Commit 2e32e0e2b82e071734919589ed680513edfd39ed in incubator-nifi's branch 
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=2e32e0e ]

NIFI-738: Improve error handling for CSV and JSON conversion.

Changes:
* Send bad record information on the "incompatible" relationship
* Use an attribute, "errors" for summarized error messages
* Send no error content for now, original content can't be accessed
* Summarize similar error messages with "N similar failures"
* Add similar error handling to CSV conversion

Signed-off-by: joewitt <[email protected]>


> Do not write conversion error messages to flow file content
> -----------------------------------------------------------
>
>                 Key: NIFI-738
>                 URL: https://issues.apache.org/jira/browse/NIFI-738
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 0.1.0
>            Reporter: Ryan Blue
>            Assignee: Ryan Blue
>             Fix For: 0.2.0
>
>
> NIFI-551 extended the error handling provided by the ConvertJSONToAvro 
> processor, but wrote error messages as the content of a file sent on the 
> failure relationship. I think the right thing to do is to output the bad 
> records as the file content and put the error messages in the outgoing 
> attributes.
> NIFI-551 wasn't included in 0.1.0, so changing this behavior is safe. 
> Consequently, I'd like to get this fix into 0.2.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to