Re: nifi is running out of memory

2016-10-31 Thread Gop Krr
Thanks Joe for checking. Yes, I got past it and I was successfully able to demo it to the team :) Now, the next challenge is to drive the performance out of nifi for the high throughput. On Mon, Oct 31, 2016 at 7:08 PM, Joe Witt wrote: > Krish, > > Did you ever get past this? > > Thanks > Joe >

Re: NiFi Real World Usage Queries

2016-10-31 Thread Joe Witt
Responses provided in-line. Apologies for the delay and brevity on some of these. Great questions all worth discsussion. On Sat, Aug 20, 2016 at 1:46 AM, Gunjan Dave wrote: > Hello NiFi Team, > Firstly, let me congratulate you on the fantastic work that your team is > doing and also on the rele

Re: nifi is running out of memory

2016-10-31 Thread Joe Witt
Krish, Did you ever get past this? Thanks Joe On Fri, Oct 28, 2016 at 2:36 PM, Gop Krr wrote: > James, permission issue got resolved. I still don't see any write. > > On Fri, Oct 28, 2016 at 10:34 AM, Gop Krr wrote: >> >> Thanks James.. I am looking into permission issue and update the thread.

Re: Processors on the fly for many sensor devices

2016-10-31 Thread Andrew Psaltis
Hi Davy, Thanks for the P/R - I merged that in just a little bit ago. I think the feature you are describing makes total sense, I'm sure this would be useful in many different use cases. I am in the process of wrapping up the changes to fulfill JIRA NIFI-2615 [1]. Do you want to add the "delimiter

Re: ExecuteSQL just once

2016-10-31 Thread Matt Burgess
Daniel, One thing you can do (albeit manually) for a "run once" is to schedule ExecuteSQL for some large interval (3600 sec for example), then start and immediately stop the processor. It will run once (stopping the processor doesn't interrupt the current execution, it just prevents it from being