Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

Thanks, Scott. That helped. On Thu, 29 Mar 2018 at 10:09 AM, James Wing wrote: > +1 (binding). Ran through the release helper, worked with a test flow. > Thanks for putting this together. > > On Mon, Mar 26, 2018 at 8:34 PM, Joe Witt wrote: > > > Hello, >

Re: ListSFTP incoming relationship

Should we really have to have an optional state saving functionality? If the user is unaware of the implications and proceed to store the state then what Andrew Grande mentioned will happen - possibilities of never ending stream of state information being stored. If we still go with the optional

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding). Ran through the release helper, worked with a test flow. Thanks for putting this together. On Mon, Mar 26, 2018 at 8:34 PM, Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi nifi-1.6.0. > > The source

Re: ListSFTP incoming relationship

Okay. So, a new processor called "ScanSFTP", allow incoming relationship where the content of the flow file is replaced with the list of matching files from the remote directory, then the list is filtered by the usual regex parameters like today. Optional state information is kept to

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding) - Ran through release helper - Setup secure NiFi and verified a test flow Sivaprasanna, I believe the issue you are seeing is due to npm not playing well with your linux distro. If you checkout latest master it contains this PR which should

Re: Anything like this been implemented yet?

I would also suggest if you want to set a static flow and not have to update data directly in NiFi, put the JSON strings in a file and use GetFile to read it in, SplitText to split it into individual lines (flowfiles), and process that way. Andy LoPresto alopre...@apache.org

Re: Anything like this been implemented yet?

Since it sounds like each query is a JSON document, can you create a JSON array of all your queries and put that as the Custom Text of a GenerateFlowFile processor? Then follow it with SplitJson to split the array into a query per flow file, assuming that is what you want. Could also use

Re: Anything like this been implemented yet?

More specifically: I know you can do this functionality by chaining other processors or using a bunch of generateflowfiles. What I'm looking for is a one stop way of associating dozens of small queries to one processor and have it batch send them on its own with no backend dependency like a

Anything like this been implemented yet?

I have a client that would benefit from being able to run certain queries periodically. Like half a dozen or more. Is there any processor where you can associate a bunch of strings (like JSON) and send them out individually as flowfiles? Thanks, Mike

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding) Followed helper to verify release, built on Ubuntu 16.04 LTS, ran the application successfully. -- Mike On Wed, Mar 28, 2018 at 2:01 PM, Mark Payne wrote: > +1 (binding) > > Was able to build successfully and start application. Created some simple > flows

Re: Docker NiFi Container superuser password

please ignore, i managed to do this by telling docker to login as root and not the default... *docker exec -i -t --user root 39dbe311249e bash * On Wed, Mar 28, 2018 at 2:06 PM, Joseph Niemiec wrote: > Hi everyone. > > Looking to change the nameservers in the default

Docker NiFi Container superuser password

Hi everyone. Looking to change the nameservers in the default docker image apache/nifi:latest but am unsure of the password... nifi@39dbe311249e:/opt/nifi/nifi-1.5.0$ su Password:

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding) Was able to build successfully and start application. Created some simple flows to verify expected behavior. Verified hashes and signing. Thanks -Mark > On Mar 26, 2018, at 11:34 PM, Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

- Confirmed hashes and signature Tried to build in a fresh Ubuntu VM that doesn't have NiFi installed or configured previously. Build fails at nifi-web-ui module. Going by how it works for others, it very well could be a isolated problem on my end. However still wanted to get this posted. Error

Re: A bug in expression substitution

Probably related to this JIRA: https://issues.apache.org/jira/browse/NIFI-4407 2018-03-28 18:42 GMT+02:00 Mark Payne : > Sergei, > > Thanks for reporting this! I have created a JIRA [1] to track this. > > -Mark > > [1] https://issues.apache.org/jira/browse/NIFI-5026 > > >

Re: A bug in expression substitution

Sergei, Thanks for reporting this! I have created a JIRA [1] to track this. -Mark [1] https://issues.apache.org/jira/browse/NIFI-5026 On Mar 28, 2018, at 7:36 AM, Sergei Zhirikov > wrote: Hi, It looks like I have stumbled upon a bug in

Re: ForkJoinPool.commonPool() in Nifi

Hi Oleksi, I'm not familiar with this part of the code but raising a JIRA sounds valid to me. If there is no fix for it, at least that is useful information and it could help other people seeing the same behavior. Pierre 2018-03-28 15:47 GMT+02:00 Otto Fowler : > I

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 I ran through the steps in the release helper guide and everything looks good. Thanks for handling RM duties, Joe. --Kevin On 3/26/18, 23:34, "Joe Witt" wrote: Hello, I am pleased to be calling this vote for the source release of Apache NiFi

Re: ForkJoinPool.commonPool() in Nifi

I would think NiFi should have it’s own thread pool. On March 28, 2018 at 09:29:31, Oleksi Derkatch (oderka...@vitalimages.com) wrote: Anyone have any thoughts on this? Should I make a JIRA ticket? From: Oleksi Derkatch Sent:

Re: ForkJoinPool.commonPool() in Nifi

Anyone have any thoughts on this? Should I make a JIRA ticket? From: Oleksi Derkatch Sent: Thursday, March 8, 2018 4:36:51 PM To: dev@nifi.apache.org Subject: ForkJoinPool.commonPool() in Nifi Hi, A few weeks ago we encountered a

Re: Read processor property in init()

Just to add on top of what Mike said. The @OnScheduled annotation indicates that the method that is marked with this annotation will run when a processor is started every time. So basically the setup() will be called and executed everytime the processor is started from the UI. On Wed, 28 Mar 2018

Re: Read processor property in init()

I will give that a go. Thanks for the quick answer, Mike! On Wed, Mar 28, 2018 at 9:01 AM, Mike Thomsen wrote: > Just do... > > @OnScheduled > public void setup(ProcessContext context) { > //Read properties and do setup. > } > > On Wed, Mar 28, 2018 at 8:57 AM, Jeff

Re: Read processor property in init()

Just do... @OnScheduled public void setup(ProcessContext context) { //Read properties and do setup. } On Wed, Mar 28, 2018 at 8:57 AM, Jeff Zemerick wrote: > Hi everyone, > > Is there a recommended method for making user-configurable property > values available to a

Read processor property in init()

Hi everyone, Is there a recommended method for making user-configurable property values available to a processor's init()? I would like to load a large index file but allow the user to specify the index's path. I am guessing that init() is executed too early to read user properties. Thanks for

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

Don't have my Linux machine on hand now so tried building on Windows 7 x64 and it fails. [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.132 s - in org.apache.nifi.wali.TestHashMapSnapshot [INFO] Running org.apache.nifi.wali.TestLengthDelimitedJournal [INFO] Tests run: 6,

A bug in expression substitution

Hi, It looks like I have stumbled upon a bug in substitution of evaluated expressions. A test case: String result = org.apache.nifi.attribute.expression.language.Query.prepare("${foo}$${foo}").evaluateExpressions(Collections.singletonMap("foo", "bar"), null); Expected result:

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 binding Built and tested flow on osx and centos Worked through release helper's guide Validates Sig's and hashes. On Wed, Mar 28, 2018, 6:10 AM Pierre Villard wrote: > +1 (binding) > > - went through the release helper guide > - full clean install on OS X > -

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding) - went through the release helper guide - full clean install on OS X - test unsecured and secured cluster setups and communications with Registry and MiNiFi Java - various flows I have are running as expected - confirmed the fix that blocked the previous RC Thanks Joe for taking

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

+1 (binding) - Confirmed hashes - Built with include-atlas profile - Confirmed various flows with 3 node secured cluster on Ubuntu - Tested integration with Hadoop environment and NiFi Registry Koji On Wed, Mar 28, 2018 at 12:27 PM, Andrew Lim wrote: > +1

Re: Rat errors building with mvn clean install -Pcontrib-check

A good way to clean the offending files is usually to do: git clean -dn (to just list the files) git clean -df (to actually delete the files) Be sure to check if you're not going to remove not committed work... Pierre 2018-03-27 18:07 GMT+02:00 Otto Fowler : > Ok, that