Provenance Events
Each point in a dataflow where a FlowFile is processed in some way is considered a provenance event. Various types of provenance events occur, depending on the dataflow design. For example, when data is brought into the flow, a RECEIVE event occurs, and when data is sent out of the flow, a SEND event occurs. Other types of processing events may occur, such as if the data is cloned (CLONE event), routed (ROUTE event), modified (CONTENT_MODIFIED or ATTRIBUTES_MODIFIED event), split (FORK event), combined with other data objects (JOIN event), and ultimately removed from the flow (DROP event).
The provenance event types are:
Provenance Event |
Description |
---|---|
ADDINFO |
Indicates a provenance event when additional information such as a new linkage to a new URI or UUID is added |
ATTRIBUTES_MODIFIED |
Indicates that a FlowFile's attributes were modified in some way |
CLONE |
Indicates that a FlowFile is an exact duplicate of its parent FlowFile |
CONTENT_MODIFIED |
Indicates that a FlowFile's content was modified in some way |
CREATE |
Indicates that a FlowFile was generated from data that was not received from a remote system or external process |
DOWNLOAD |
Indicates that the contents of a FlowFile were downloaded by a user or external entity |
DROP |
Indicates a provenance event for the conclusion of an object's life for some reason other than object expiration |
EXPIRE |
Indicates a provenance event for the conclusion of an object's life due to the object not being processed in a timely manner |
FETCH |
Indicates that the contents of a FlowFile were overwritten using the contents of some external resource |
FORK |
Indicates that one or more FlowFiles were derived from a parent FlowFile |
JOIN |
Indicates that a single FlowFile is derived from joining together multiple parent FlowFiles |
RECEIVE |
Indicates a provenance event for receiving data from an external process |
REPLAY |
Indicates a provenance event for replaying a FlowFile |
ROUTE |
Indicates that a FlowFile was routed to a specified relationship and provides information about why the FlowFile was routed to this relationship |
SEND |
Indicates a provenance event for sending data to an external process |
UNKNOWN |
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 |