Thanks Joe for quick response. I agree it can be implemented with either of the approach you suggested. But both approaches are more cumbersome to implement.
Do you think it will be worth to explore adding such an attribute ? I think it will be of value to other developers also during development of flow. I am new to JAVA development but I can help in contributing to this development. On a separate note - Is there a way to access provenance trail for this information dynamically ? Thanks. Shishir -----Original Message----- From: Joe Witt [mailto:[email protected]] Sent: Thursday, June 16, 2016 11:35 AM To: [email protected] Subject: Re: Attribute for current Processor/Connection Hello We do not automatically tag the flow file attributes with sourcing information. That is captured in the provenance trail though. For your case you might consider adding an update attribute processor after each transition point where you want to capture something of interest so you can tag the attributes. Then your single group for error handling will have the needed context. Alternatively, you can put input ports on your error handling process group which are inherently about the context of data they intend to receive. Thanks JOe On Thu, Jun 16, 2016 at 11:32 AM, Saxena, Shishir <[email protected]> wrote: > Hi, > Is there any attribute available on every flow that will give details on > what was the last processor that processed the flow ? I have a flow where I > am routing all failures to a single process group for error handling. It will > be convenient to have an attribute for current processor, so any error > messages can be generated based on which processor failure occurred. > > Thanks for any help. > > Shishir > > > > > > This email transmission and any accompanying attachments may contain CSX > privileged and confidential information intended only for the use of the > intended addressee. Any dissemination, distribution, copying or action taken > in reliance on the contents of this email by anyone other than the intended > recipient is strictly prohibited. If you have received this email in error > please immediately delete it and notify sender at the above CSX email > address. Sender and CSX accept no liability for any damage caused directly or > indirectly by receipt of this email.
