[
https://issues.apache.org/jira/browse/NIFI-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215823#comment-16215823
]
Scott Reisdorf commented on NIFI-3453:
--------------------------------------
Thanks for the input, but I dont think that would help my situation.
I use Provenance events to report back not only when a processor for a flow
file has completed, but also in understanding the state of the flow file as it
passed through the processor. If I added an UpdateAttributes processor after
the different processors in the flow to add some state to the flow file, it
still doesn't help when examining ProvenanceEvents in determining the actual
processor (in this case the one prior to this update attributes) in my flow
file that failed. I think it would put me in the same situation I am in now
and just help me in determining some state of the flow file (which I do now via
inspecting the connection relationship the flow file took), but not actually
tell me the exact processor that failed.
The provenance already has the connection identifier indicating the connection
it passed through. If the relationship data was populated for each provenance
event, then one could use the provenance to construct the full graph of the
flow file and the realtionships the flow took in its connections.
> Provenance Events dont have the "relationship" from where the event came
> ------------------------------------------------------------------------
>
> Key: NIFI-3453
> URL: https://issues.apache.org/jira/browse/NIFI-3453
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.2.0, 1.0.1, 1.3.0
> Reporter: Scott Reisdorf
> Attachments: Screen Shot 2017-02-09 at 5.36.08 AM.png
>
>
> I have a reporting task that processes the Provenance Events in NiFi.
> I would like to know the relationship the event came from; however, that
> field doesn't seem to be getting populated. (screenshots attached).
> No matter what processor or flow I create the "relationship" field is always
> null.
> I am running with NiFi 1.0.1,
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
