You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2016/06/22 17:16:57 UTC
[jira] [Created] (NIFI-2085) Emit Route provenance event with
details when processor fails and transfers flowfile
Joseph Percivall created NIFI-2085:
--------------------------------------
Summary: Emit Route provenance event with details when processor fails and transfers flowfile
Key: NIFI-2085
URL: https://issues.apache.org/jira/browse/NIFI-2085
Project: Apache NiFi
Issue Type: Improvement
Reporter: Joseph Percivall
Originally hit here[1], as a user multiple FlowFiles were routed to "failure" and I didn't know why. Looking at provenance I realized that since ExtractMediaMetadata didn't emit a provenance event, I wasn't able to figure out exactly why the FlowFile failed. What I would like is for a Route event to be emitted when the FlowFile is transferred to failure. This Route event would contain details of the exception that was caught.
This can be applied to any processor where there is a default "failure" relationship, nothing happens to the flowfile and it is just trasnferred.
This hasn't been best practice because many times the "failure" relationship is routed back to the processor and can cause huge amounts of provenance events to be created. This is blocked by NIFI-104.
[1] https://github.com/apache/nifi/pull/556
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)