Re: NiFi retry capabilities

Bryan, you managed to explain it in three sentences! :) now I get it! thanks a bunch On Tue, Mar 6, 2018 at 4:23 PM, Bryan Bende wrote: > Boris, > > "Penalty Duration" is per flow file, and "Yield" is for the processor. > > If the processor penalizes a flow file and transfers

Re: NiFi retry capabilities

Boris, "Penalty Duration" is per flow file, and "Yield" is for the processor. If the processor penalizes a flow file and transfers it to a queue, whatever is processing that queue won't take that flow file from the queue until the penalty duration has passed. If a processor yields, then the

Re: NiFi retry capabilities

Hi Mark, thanks for your response! especially because I saw your name in that Jira :) I think it makes sense to "keep trying until you're successful". I am a bit confused by "yield" and "penalize" parameters. Can you give me an example how they are used? Let's say, I use ExecuteSQL processor

Re: NiFi retry capabilities

Hey Boris, Using the UpdateAttribute and RouteOnAttribute approach is only necessary when you want to retry N number of times (or for some time period) and after that elapses to treat the data differently. Most of the time, though, what is used is to simply loop the 'failure' relationship back

NiFi retry capabilities

Just found this Jira https://issues.apache.org/jira/browse/NIFI-90 I am surprised it has not got any traction after 3 years...Having used Apache Airflow for a while, I am looking to retry capabilities in NiFi and it seems it comes down to "build your own" flow approach, that would handle retries