nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <>
Subject [jira] [Commented] (NIFI-1018) Allow ControllerServices access to ProvenanceReporter
Date Fri, 02 Oct 2015 19:14:26 GMT


Joseph Witt commented on NIFI-1018:

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

> Allow ControllerServices access to ProvenanceReporter
> -----------------------------------------------------
>                 Key: NIFI-1018
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message