You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dan Shevenell (JIRA)" <ji...@apache.org> on 2018/07/09 16:32:00 UTC

[jira] [Updated] (NIFI-5397) Parent processor's ID & relationship as core FlowFile attributes

     [ https://issues.apache.org/jira/browse/NIFI-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Shevenell updated NIFI-5397:
--------------------------------
    Summary: Parent processor's ID & relationship as core FlowFile attributes  (was: Parent processor's ID & relationship as constantly updating FlowFile attributes)

> Parent processor's ID & relationship as core FlowFile attributes
> ----------------------------------------------------------------
>
>                 Key: NIFI-5397
>                 URL: https://issues.apache.org/jira/browse/NIFI-5397
>             Project: Apache NiFi
>          Issue Type: Wish
>            Reporter: Dan Shevenell
>            Priority: Trivial
>
> My team has a use-case where being able to access FlowFile attributes of ...
>  * Parent processor's ID
>  * Routing relationship (e.g. "success", "failure", "matched", etc.)
> ... would be exceptionally helpful.
>  
> *Request:*  By default, have each processor update {color:#59afe1}parent.processor.id {color}{color:#333333}and {color:#59afe1}parent.relationship{color} flowfile attributes.{color}
>  
> Use-case specifics:
>  * We've built a GUI where edge operators submit data back to a remote, central repository. 
>  * Operators won't know anything about NiFi / the underlying data processing chains.
>  * Being able to simply "chirp" back processor ID + relationship to the GUI would allow us to provide light, "provenance-like" status to the remote edge operator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)