I have a similar issue. I wonder if you have found an answer already. Was that community helpful? ... View more

if possible please share processor configuration sreen-shot ... View more

thanks @shu its working like charm @Shu ... View more

@Mitthu Wagh We can use Wait-Notify processors to wait for 2 Target Signal Count then wait processor releases the flowfile once target signal count number reaches to 2. Refer to this link for usage/configuring wait/notify processors. Another way is by using MergeContent processor with correlation attribute name and Minimum number of entries as 2 then processor will wait for 2 flowfiles with the same attribute name then merges the flowfiles and then send mail based on that. Refer to this and this links for same use case with mergecontent processor. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@Mitthu Wagh You can use UpdateAttribute Processor by storing the state and incrementing the last state value then pass the attribute value to get HTTP response. Flow: As GetHTTP processor doesn't accept any incoming connections use InvokeHTTP processor instead of GetHTTP processor. UpdateAttribute Configs: In this processor i'm using getStateValue function to get the value for the variable and adding one to it so output flowfile from UpdateAttribute will have seq attribute with 1 as value in your first run. Then use the attribute in your InvokeHTTP processor to increment the page number. Refer to this link if you want to reset the state once the number reaches to limit. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

Hi Mitthu, Here is an article I wrote about handling failures in NiFi: https://community.hortonworks.com/articles/76598/nifi-error-handling-design-pattern-1.html It describes how to retry failures X times, then send an email, then wait for administrative input. This might help you address the requirements of your solution. You could also add a PutEmail processor on the "Success" relationship to send an email after processing succeeds. ... View more

With nifi 1.3 you have the record based processors. So you can forward the output of executesql or your custom processor to QueryRecord. Set it up to read Avro. Now add a query like so select col_a,col_b..'${query_id}','${query_time}','${query_end_time}' from flowfile'. this will add the data you need to the query resultset. ... View more

Since you're using a script, you could feasibly replace steps 4-7 above, but my blog post (plus adding your attribute) really only covers 5&6 ... View more

Do you have an error ? ... View more