RE: [EXT] Re: Automated Testing of Flows

2017-11-16 Thread Peter Wicks (pwicks)
I don't even know if I need Jenkins to setup a fresh instance, that could be nice, but I could use my TEST instance and just upgrade it by hand anytime I want to test a new version. I could create a dedicated Process Group that my test scripts would use for deploying the templates. I've worked

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.3.0

2017-11-16 Thread Aldrin Piri
Marc, Thanks for the update and rounding up these last few issues. The timeline sounds good to me and appreciate you taking on the RM duties. I have some notes and such that should go for updating/crafting the release guide for C++ land. Things have changed a fair bit since our 0.2.0 release,

Re: build failure

2017-11-16 Thread Aldrin Piri
Hi Mark, Not sure of the exact cause, but I believe others were running into this issue and it was remedied by the work in https://github.com/apache/nifi/pull/2273. On Thu, Nov 16, 2017 at 9:46 PM, Mark Bean wrote: > I'm getting build failures when I attempt to build the

Re: Automated Testing of Flows

2017-11-16 Thread Scott Aslan
Just brain storming here You could use travis or Jenkins to setup a job where you use mvn and npm to build and start NiFi. Assuming the test template was available from within the environment maybe you could use the protractor e2e testing suite to script the clicks necessary to load the

build failure

2017-11-16 Thread Mark Bean
I'm getting build failures when I attempt to build the latest master on one environment but not another. The failure was on macOS 10.12.6, maven 3.3.9, java 1.8.0_74. I agree, some of those could (and will be soon) updated. Yet, I was able to build successfully on an AWS EC platform earlier

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.3.0

2017-11-16 Thread Marc
Everyone, It looks as though the issues mentioned yesterday have been solved for 0.3.0. I apologize for being the long pole in addressing these issues in a release that has seen some great work by a great group of contributors. A new ticket was created in response to an issue that helped

Run 1 instance of ExecuteStreamCommand constantly

2017-11-16 Thread moe2017
Hey, I have python machine learning model being executed my an ExecuteStreamCommand processor. The problem right now is that I need this processor to be executed once and then consistently loop so that the model can update itself when new data is passed to it from stdin. I tried putting in a

Re: Issue with Executescript

2017-11-16 Thread Vyshali
I have subscribed. -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Issue with Executescript

2017-11-16 Thread Joe Witt
It is awesome that you're using NiFi and engaging with the community. However, please subscribe to the mailing list. I will no longer manually moderate these which mean they will not be seen unless you subscribe or another moderator chooses to manually moderate. If you're unsure how to subscribe

Re: Issue with Executescript

2017-11-16 Thread Vyshali
Hi andy, I have successfully written the coding logic to do anonymization and was able to execute it without error. But I'm getting different results while running the same script on the same input in Nifi and as a normal python script.I'm not sure what is the problem. Sample dataset :