[
https://issues.apache.org/jira/browse/NIFI-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133174#comment-15133174
]
Brandon DeVries commented on NIFI-1018:
---------------------------------------
That could also potentially help distribute data sets across nodes, and
make sure data sets are in sync. That would be a lot better than our
current ad hoc solutions...
> 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)
