You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/10/15 22:07:06 UTC
[jira] [Created] (NIFI-1038) FetchS3Object emits wrong Provenance
Event
Mark Payne created NIFI-1038:
--------------------------------
Summary: FetchS3Object emits wrong Provenance Event
Key: NIFI-1038
URL: https://issues.apache.org/jira/browse/NIFI-1038
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Mark Payne
Assignee: Mark Payne
Fix For: 0.4.0
>From the users@ mailing list, we received a question regarding FetchS3Object. The processor reports a RECEIVE provenance event. However, it does not create the FlowFIle (it overwrites the contents of a FlowFile) so RECEIVE is the wrong Provenance event. This should be a CONTENT_MODIFIED event, or preferably a FETCH event, when that has been implemented. The email received is below:
I understand that FetchS3Object processor requires an incoming FlowFile to trigger it. The problem is that FetchS3Object emits a RECEIVE provenance event for the existing FlowFile. That event causes following error when I try to open the lineage chart for a simple flow: GenerateFlowFile -> FetchS3Object.
"Found cycle in graph. This indicates that multiple events were registered claiming to have generated the same FlowFile (UUID = 40f58407-ea10-4843-b8d1-be0e24f685aa)"
Should FetchS3Object create a new FlowFile for each fetched object? If so, does it really require an incoming FlowFile?
Regards,
Ben
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)