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

Michael Moser commented on NIFI-1018:
-------------------------------------

I wonder if the new StateManager could be leveraged in any way?  Can Controller 
Services access the StateManager?  Can FlowFile references be stored in the 
StateManager in such a way that it could be used in a ProvenanceReporter?

> 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
>            Assignee: Michael Moser
>
> 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)

Reply via email to