juldrixx commented on PR #6011: URL: https://github.com/apache/nifi/pull/6011#issuecomment-1117593484
> I'm a bit confused by this change. You're adding the attribute to the original flow file but one could configure many dynamic properties with different queries and there could be many different relationships (one per query). I don't think the change makes sense given how the processor can be used. I'm adding the attibrute to the original flow file in two cases: when the flow file goes in failure queue and in original queue but when the flow file goes to "query" queue and becomes a "transformed" flow file, I add the attribute with name of the "query queue". To summarise: - if the flow file goes to failure, the failure queue name is put in the attribute. - if the flow file goes to original, the original queue is put in the attribute. - if the flow file goes to "query" queue, the query name is put in the attribute. I did this to copy what is done in RouteOnAttribute to have an attribute to use to factor out part of the process after the processor with a condition on that attribute. I'm not sure if its clearer? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
