[
https://issues.apache.org/jira/browse/NIFI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604574#comment-14604574
]
ASF GitHub Bot commented on NIFI-738:
-------------------------------------
Github user rdblue commented on the pull request:
https://github.com/apache/incubator-nifi/pull/69#issuecomment-116218005
Thanks for taking a look, Joe.
I implemented the changes as you suggested. I kept the incompatible
relationship because when we can recover the original content, I intend to
filter out the successful records and send just the failures. But you're right
that for now we should include the original data to make it easier to debug
flows.
For the failure tracker, I updated it to keep just the first full error
message and a counter instead of the multimap. I don't think it will be a
memory problem now.
> 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)
