[
https://issues.apache.org/jira/browse/NIFI-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Percivall updated NIFI-979:
----------------------------------
Issue Type: Sub-task (was: Task)
Parent: NIFI-1028
> Document how a user can track the lineage of an object that went through nifi
> multiple times
> --------------------------------------------------------------------------------------------
>
> Key: NIFI-979
> URL: https://issues.apache.org/jira/browse/NIFI-979
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Documentation & Website
> Reporter: Joseph Witt
> Assignee: Joseph Percivall
> Priority: Minor
>
> Thanks for the pointer, Joe! I will be going through them.
> My exact problem is I am trying to think if I can trace a message through the
> system; something like a message entering NiFi, leaving it, and then
> reentering it, & NiFi recognising that this is the same flow that is still
> going through.
> Consider the scenario:
> HTTP request coming in through a web server.
> This goes to backend for processing & a copy (or some attribute to ID this
> request) goes to NiFi.
> The backend processes this request & then sends a copy (or the attribute
> identifying the message & its response) to NiFi.
> Web server responds to the request.
> In NiFi, I should be able to trace the request from web-server to backend to
> response.
> Is this possible? Can NiFi link the different messages it receives at
> different times based on some unique ID?
> --
> κρισhναν
> Krish,
> Yes. If it is two different times that the same 'concept of an object' goes
> through NiFi then there will be two provenance trails. You can add
> attributes to be indexed though in NiFi by adjusting the appropriate
> properties for provenance indexing in nifi.properties. With this you can
> index whichever attribute you have in mind that will hold this correlation
> attribute. As a result you can given finding one correlation identifier find
> all paths that the object took through the system even if it is multiple
> trips.
> There is a supported concept called 'associated object identifier' but I am
> not sure we already have the user experience in place for that. We really
> should document this entire concept because this is a great question and a
> common question as folks start to realize the power of provenance. That JIRA
> can be found here [1]
> Thanks
> Joe
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
