You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Ricky Saltzer (JIRA)" <ji...@apache.org> on 2015/04/28 22:05:06 UTC
[jira] [Updated] (NIFI-551) Improve error handling for
ConvertJSONToAvro processor
[ https://issues.apache.org/jira/browse/NIFI-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ricky Saltzer updated NIFI-551:
-------------------------------
Attachment: NIFI-551.1.diff
Attaching a first pass patch
{code}
NIFI-551 - ConvertJSONToAvro improve error message
- Report failure counts as an log error message
- Send record parsing errors to a separate flowfile which is transfered down the
failure relationship
{code}
I wonder if I should create a new relationship just for the failure messages, since we also sometimes send the entire flowfile of records if we encounter a _ProcessException_ or _DatasetException_
> Improve error handling for ConvertJSONToAvro processor
> ------------------------------------------------------
>
> Key: NIFI-551
> URL: https://issues.apache.org/jira/browse/NIFI-551
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Ricky Saltzer
> Attachments: NIFI-551.1.diff
>
>
> 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)