Re: Routing to Failure relationships and Route provenance events

Hello Michal, On a previous project, I worked on a flow with hundreds of processors that handled thousands of files per day, and had similar questions when I was trying to figure out the best way to figure out how to handle failures gracefully to make it possible to automatically retry processing

Re: nifi configuration file for process group

Bala, Let me add to the below in saying that in the current implementation of custom properties, variables are bound at startup. So if the custom property file is changed then nifi would need to be restarted. However there are jiras and discussion around improving this in the future. Yolanda On

Re: nifi configuration file for process group

Hello Bala, If you are using a processor that supports expression language for the IP address property you can configure NiFi to use a variable within a custom property file that you define. Once that is set you can refer to the custom variable in the IP field instead of the raw IP value. For

Re: nifi configuration file for process group

Hello Bala, Are all your processors HTTP processors? Which processors are you trying to use to grab data from the IP? You may want to think about whether you could use just a couple processors and update them by hand. If you have to have many processors that hit the same IP, they all can accept

nifi configuration file for process group

Hi all, My use case is, 1)Process group A is having 10 processors which uses same ip address ex(192.168.1.1) for some processing. ex http post 2) if this ip address is changed, i need to update all the processors. 3) is there any way i can handle this in a configuration file in nifi? ex:

Re: [DISCUSS] NiFi 1.1.0 release

Andy, Great to see NIFI-3050 implemented and certainly good news that NiFi 1.1.0 is set to include a number of security related improvements. On Thu, Nov 17, 2016 at 2:38 PM, Andy LoPresto wrote: > Just updating this thread that NIFI-3050 [1] and NIFI-3051 [2] have been

Re: Routing to Failure relationships and Route provenance events

Hi, thank you both for responses. I understand the scenario with rerouting back to processor would cause infinite provenance history. It can also cause inifite loop, when the destination system is offline, therefore I am not using this approach in this case. Generaly, I have problem identifying