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 Witt (JIRA)" <ji...@apache.org> on 2015/10/02 21:14:26 UTC

[jira] [Commented] (NIFI-1018) Allow ControllerServices access to ProvenanceReporter

    [ https://issues.apache.org/jira/browse/NIFI-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941588#comment-14941588 ] 

Joseph Witt commented on NIFI-1018:
-----------------------------------

++1!  Big fan of this idea.  Plays nicely with [~markap14]'s plans to have FETCH_CONTENT event too.

> Allow ControllerServices access to ProvenanceReporter
> -----------------------------------------------------
>
>                 Key: NIFI-1018
>                 URL: https://issues.apache.org/jira/browse/NIFI-1018
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Brandon DeVries
>
> Currently we maintain a provenance trail for all files flowing through NiFi Processors.  However, if a ControllerService uses some data set it generally just loads it from disk after it is fetched using a normal NiFi flow.  However, this breaks the provenance trail for the data set... there is no way (in provenance terms) of knowing what data set the ControllerService is using or when it was loaded.  By giving ControllerServices access to the ProvenanceReporter, they can acknowledge "receipt" of a data set, so the provenance trail from pull to use is maintained.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)