Adding Functionality to Apache NiFi
Also available as:
loading table of contents...

Provenance Events

The different event types for provenance reporting are:

Provenance Event Description


Indicates a provenance event for adding additional information such as new linkage to a new URI or UUID


Indicates that a FlowFile's attributes were modified in some way. This event is not needed when another event is reported at the same time, as the other event will already contain all FlowFile attributes


Indicates that a FlowFile is an exact duplicate of its parent FlowFile


Indicates that a FlowFile's content was modified in some way. When using this Event Type, it is advisable to provide details about how the content is modified


Indicates that a FlowFile was generated from data that was not received from a remote system or external process


Indicates that the contents of a FlowFile were downloaded by a user or external entity


Indicates a provenance event for the conclusion of an object's life for some reason other than object expiration


Indicates a provenance event for the conclusion of an object's life due to the object not being processed in a timely manner


Indicates that the contents of a FlowFile were overwritten using the contents of some external resource. This is similar to the RECEIVE event but varies in that RECEIVE events are intended to be used as the event that introduces the FlowFile into the system, whereas FETCH is used to indicate that the contents of an existing FlowFile were overwritten


Indicates that one or more FlowFiles were derived from a parent FlowFile


Indicates that a single FlowFile is derived from joining together multiple parent FlowFiles


Indicates a provenance event for receiving data from an external process. This Event Type is expected to be the first event for a FlowFile. As such, a Processor that receives data from an external source and uses that data to replace the content of an existing FlowFile should use the FETCH event type, rather than the RECEIVE event type


Indicates a provenance event for replaying a FlowFile. The UUID of the event indicates the UUID of the original FlowFile that is being replayed. The event contains one Parent UUID that is also the UUID of the FlowFile that is being replayed and one Child UUID that is the UUID of the a newly created FlowFile that will be re-queued for processing


Indicates that a FlowFile was routed to a specified relationship and provides information about why the FlowFile was routed to this relationship


Indicates a provenance event for sending data to an external process


Indicates that the type of provenance event is unknown because the user who is attempting to access the event is not authorized to know the type