[
https://issues.apache.org/jira/browse/NIFI-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215762#comment-16215762
]
Joseph Witt commented on NIFI-3453:
-----------------------------------
[~scott.reisdorf] it can be tough to know where to draw the line in terms of
the amount of fidelity we generate automatically in provenance data. As Mark
points out the relationship mechanism is there now and automatically used by
Route events. If we used it more often it would mean likely using it all the
time then we run the other problem of making a lot of data someone might likely
not use. Alternatively, you could 'opt-in' to such level of detail by
leveraging flowfile attributes and using UpdateAttribute to inject the
details/specificity you need on specific connections. Have you considered that?
> 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)
