Re: Problems with ListenBeats 1.3.0

Nick, I use it with: filebeat: spool_size: 2048 output.logstash: compression_level: 2 bulk_max_size: 100 timeout: 30 On the NiFi side I have: Receive Buffer Size: 128KB Max Size of Message Queue: 1 Max Size of Socket Buffer: 2MB Can you try and let me know? Perhaps something

Re: Problems with ListenBeats 1.3.0

It seemed to hold up a little bit better but I ended up getting the same errors. On Thu, Aug 24, 2017 at 11:35 AM, Nick Carenza < nick.care...@thecontrolgroup.com> wrote: > Okay, thank you Andre! > > - Nick > > On Wed, Aug 23, 2017 at 4:03 PM, Andre wrote: > >> Nick, >> >>

Re: Production Deployment

Looking forward to reading your thoughts, Andy. Dan Young [1][2], Chris Herrera [3][4], and Roger Carhuatocto [5][6] have been fairly active in writing about their selection of NiFi and how they use it in their worlds. [1] https://looker.com/blog/leveraging-apache-nifi-for-agile-dataflows

Re: ListSFTP/FetchSFTP not running after bad password

No problem, I will work on it. [image: Payoff, Inc.] *Jeremy Farbota* Software Engineer, Data Payoff, Inc. jfarb...@payoff.com On Thu, Aug 24, 2017 at 11:38 AM, Joe Witt wrote: > Jeremy > > Can you please file a JIRA to cover this scenario that you're observing. > If you

Re: ListSFTP/FetchSFTP not running after bad password

Jeremy Can you please file a JIRA to cover this scenario that you're observing. If you can share stack traces/thread dumps/logs. I agree this sounds like poor behavior and we should definitely make it better. On Thu, Aug 24, 2017 at 2:04 PM, Jeremy Farbota wrote: > I have

Re: Problems with ListenBeats 1.3.0

Okay, thank you Andre! - Nick On Wed, Aug 23, 2017 at 4:03 PM, Andre wrote: > Nick, > > This is a bug (NIFI-3753). I am also able to confirm there is a > workaround: just change the compression settings to a lower compression > level (I believe anything between none and 3

ListSFTP/FetchSFTP not running after bad password

I have a ListSFTP process that I've been using for a few months where a partner posts some large files, I turn it on, then ListSFTP gets all the filenames so a FetchSFTP can download them prior to other steps and notification events later on. I had an issue this month initially because a password

Production Deployment

Hey team, I've been really impressed with Nifi. Thanks for sharing! I'm working on preparing an environment and workflow for a production product. I'll be producing some fairly generic documentation on how I run Nifi on AWS - what works for me and the reasons for choosing the operating model.

Re: Multiple or statements

Nice, thank you! On 2017-08-24 08:46, Mark Payne wrote: Laurens, Certainly, you can: ${field:startsWith('alpha'):or( ${field:startsWith('beta')} ):or( ${field:startsWith('gamma')} )} Or, alternatively, you could use a regex: ${field:matches( '(alpha|beta|gamma).*' )} Thanks -Mark

Re: Multiple or statements

Laurens, Certainly, you can: ${field:startsWith('alpha'):or( ${field:startsWith('beta')} ):or( ${field:startsWith('gamma')} )} Or, alternatively, you could use a regex: ${field:matches( '(alpha|beta|gamma).*' )} Thanks -Mark > On Aug 24, 2017, at 11:06 AM, Laurens Vets

Multiple or statements

Hi list, Is it possible to have multiple 'or' statements in the query language? What I want to do is route on a JSON attribute if it doesn't start with 'alpha', 'beta' or 'gamma'. Is it possible to add a 3rd condition to the following somehow: ${field:startsWith('alpha'):or(

Re: [EXT] High-performance Nifi decoder

Hi Peter, It hasn't been finalized yet, but we can configure it to be reasonably low. Basically the higher batch size. In regards to my question, which strategy you think will provide more throughput? Regards, Ali On Wed, Aug 23, 2017 at 6:49 PM, Peter Wicks (pwicks) wrote: