Re: Custom processor is failing for concurrency

Kumiko, would it be sufficient to just wrap your call to the non-thread-safe MS SDK routine, in a 'synchronized' method? You could then use the standard NiFi thread management and avoid a lot of complexity. And the result should be >= efficiency of having a dedicated thread to manage the

Re: Custom processor is failing for concurrency

. From: Oleg Zhurakousky <ozhurakou...@hortonworks.com> Sent: Thursday, June 09, 2016 12:15 PM To: users@nifi.apache.org Cc: Kevin Verhoeven; Ki Kang Subject: Re: Custom processor is failing for concurrency +1, was just responding with the same. On Jun 9, 2016, at 3:11 PM, Matt

Re: Custom processor is failing for concurrency

thing? For the line 209: synchronized (this) { SetupClients(creds); if (creds!= null) { return creds; } For the line 217: synchronized { CreateFile(_path + _filename, value.get(), true); } Thanks Kumiko From: Matt Foley [mailto:mfo...@hortonwo

Re: new Nifi Processors

Hi Uwe, Most everything about Apache licensing, and how it relates to other licenses such as GPL (from the Apache viewpoint) is in these two faqs: http://www.apache.org/foundation/license-faq.html https://www.apache.org/legal/resolved --Matt From: Uwe Geercken

Re: How to gracefully handle a circular graph?

If I understand correctly, your desired goal is for each input row that specifies a range, A to A+N, you would generate a sequence of N (or perhaps N+1) flowfiles, right?  And the only difference in each flowfile is that you’ve Replaced the range specification with a single number from that

Re: Providing Config and Attributes to NiFi

Hi Joe, The specification document in the wiki is written in future tense, but is it in fact what got implemented in the two jiras (all linked below)? Thanks, --Matt On 3/24/17, 5:50 AM, "Joe Witt" wrote: James, In NiFi 1.x line we introduced the variable