[
https://issues.apache.org/jira/browse/NIFI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606354#comment-14606354
]
ASF GitHub Bot commented on NIFI-738:
-------------------------------------
Github user rdblue commented on the pull request:
https://github.com/apache/incubator-nifi/pull/69#issuecomment-116838575
I think this is ready to go. I'm not concerned with the error tracking
because we keep to a pretty reasonable format, "General error: specific data".
The general errors will be stored along with a count and a single full error
message. We don't have very many possibilities for that, usually "Can't convert
to <type>" or "Field <name>", both of which are pretty limited.
> 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)
