[
https://issues.apache.org/jira/browse/NIFI-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133091#comment-15133091
]
Michael Moser commented on NIFI-1018:
-------------------------------------
As a really crazy idea, I wonder if it would be useful for NiFi to have a new
Configuration Repository? It would consist of FlowFiles that are more-or-less
permanent. They could be stored in the Configuration Repository with a unique
key, so it would be easy to replace with an updated file. Provenance events
could be recorded for when FlowFiles add/update/delete from the Config
Repository. Processors/Services/Tasks could reference the FlowFiles in the
Configuration Repository by this unique key, and could record a provenance
event when they use this reference to read a FlowFile.
> 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)
