@linssab ,   You are probably running into this issue described in NIFI-9241, which has been fixed on NiFi 1.15.   Cheers, André   ... View more

@sayak17  If you are simply looking to GET from a REST API endpoint and take the response and write to a local file on the server where your NiFi service is running, you'll want to use the InvokeHTTP processor and feed that to your putFile processor.   If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt ... View more

Hello @stale , Have you already fix this issue? I am facing the same problem with same version 7.6.5 on kerberized cluster ... View more

@araujothe next step is with InvokeHTTP processor to update the stocks of products via Rest Endpoint ... View more

Issue created : https://issues.apache.org/jira/browse/NIFI-10197 ... View more

@pk87  Also consider that using timer driven may not always give you 60 minute scheduling.  When using timer driven the component will get scheduled upon start and then again x configured amount of time later.  A NiFi restart or stopping and starting the processor will reset this.  If you need to make sure that a component is only scheduled every x amount of time consistently, you should be using cron driven scheduling strategy which will allow you to set specific time of schedule. Thanks, Matt ... View more

@roshanbi Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks ... View more

@harvey ,   You are probably running into the problem described in this Technical Service Bulletin. Please check the bulletin for the solution/workaround.   Cheers, André   ... View more

Thanks, I have filed a JIRA bug: https://issues.apache.org/jira/browse/NIFI-10171 ... View more