[
https://issues.apache.org/jira/browse/NIFI-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523679#comment-14523679
]
Joseph Witt commented on NIFI-551:
----------------------------------
Ricky
We've ended up doing precisely what you've just proposed here for very similar
cases before. Totally with you on doing the best you can for getting the user
something contextually meaningful to help them figure out the root cause.
I think though what mark is pointing out is that if in FlowFile A containing
records 1...N if record N-M fails to parse you throw out FlowFile A and instead
generate an error message and send that message. I would recommend you send
FlowFile A to failure and on flowfile A you add an attribute which is the error
summary like you propose.
I could be interpreting both you and Mark incorrectly and if so feel free to
ignore me :-)
Thanks
Joe
> Improve error handling for ConvertJSONToAvro processor
> ------------------------------------------------------
>
> Key: NIFI-551
> URL: https://issues.apache.org/jira/browse/NIFI-551
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Ricky Saltzer
> Labels: patch, review
> Fix For: 0.1.0
>
> Attachments: NIFI-551.1.patch, NIFI-551.2.patch
>
>
> Currently, if the ConvertJSONToAvro processor fails to process an individual
> record, a counter is incremented, but no alerts are produced. It would be
> better to notify the bulletin board that we've failed to process some records
> for a flowfile. Further, we should stream the records we fail to process down
> the failure relationship for further inspection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
