Kylo reports the processing node coming AFTER the node actually failed as "FAILED"

Description

If a processing node routes the flow file to its "FAILURE" output queue, the node itself and not the next one fetching the flow file from the "FAILURE" queue should be marked as failed in Kylo UI.

This behaviour can be very confusing for the end user.

The failure handling logic in com.thinkbiganalytics.nifi.provenance.ProvenanceFeedLookup#setProcessorFlowType is incomplete, as it simply checks the INCOMING queue's name, and marks the CURRENT event as FAILURE if the incoming queue is a FAILURE queue. This is inconsistent, as the event for the (previous) node routing the flow file to the FAILURE queue is the one, where processing failed.

com.thinkbiganalytics.nifi.provenance.ProvenanceFeedLookup#setProcessorFlowType

Environment

None

Assignee

Unassigned

Reporter

Peter Horvath

Labels

None

Reviewer

None

Story point estimate

None

Affects versions

Priority

Medium
Configure