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

Joey, I am curious about the test failure. That is the test I refactored due to the POSIX attribute issue failing on Windows right before the RC. It passed when I built on Linux so if you can open a Jira or at least provide me with a stack trace and any steps to make it reproducible, I would

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

+1 (non-binding) Full build and test finished successfully without any issue on OS X. Here are the things that I look forward in future improvements (didn't check existing JIRAs): -- 1. minifi.sh restart does not working?

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

+1 (binding) release this package as nifi-1.2.0 Verified hashes & commit, full clean build w/contrib check on OSX El Capitan, ran CDC (MySQL to Oracle) flow which exercises the Schema Registry and JsonTreeRecordReader as well. On Fri, May 5, 2017 at 10:07 PM, Bryan Bende

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

+1 (binding). Was able to complete full build w/ contrib check on OSX. Verified checksums and that a quick test of functionality looks good. > On May 5, 2017, at 10:07 PM, Bryan Bende wrote: > > Hello, > > I am pleased to be calling this vote for the source release of

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

+1 (non-binding) Release this package as nifi-1.2.0 There was definitely a lot of work that went into this release, many thanks to all. On Mon, May 8, 2017 at 2:23 PM, Mark Payne wrote: > +1 (binding). > > Was able to complete full build w/ contrib check on OSX. Verified

Re: [CANCEL][VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC1)

+0 (1 Test is failing for me) * Sig Validated * Hashes Validated * Built on Ubuntu 14.04 [Used Ubuntu Package libleveldb1 & cmake 3.2 successfully: Linux edge1 4.4.0-75-generic #96~14.04.1-Ubuntu SMP Thu Apr 20 11:06:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux] * Running tests I hit a segfault,

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

+1 binding - release this package as nifi-1.2.0 * confirmed keys, hashes, and commit. * built with tests and contrib-check on CentOS 7.3.1611, JDK 1.8.0_121, and Maven 3.3.9. * checked the README, LICENSE, and NOTICE files. * ran convenience binary with minimal flow that performed as expected.

Re: Pulling out hair over slf4j...

Russell, In looking at the NiFi 1.1.2 pom [1] it appears that NiFi uses version 1.7.12 of slf4j, and two of the slf4j dependencies are not marked with the scope of provided. Specifically, slf4j-log4j12 and slf4j-simple. That may be causing the issue you are seeing. Is it possible you can exclude

Re: Issue with NiFi Data Container.

Dear Nifi Experts, May i request for your review and suggestion? How can i gracefully stop all nifi processes by executing docker nifi stop. Regards Gaurav Goyal On Fri, May 5, 2017 at 3:56 PM, Gaurav Goyal wrote: > I have created nifi docker image. > When i run into

Re: Pulling out hair over slf4j...

Russell, Assuming you have the standard project structure with a pom and then sub-modules for processors and NAR, does your root pom have a parent of nifi-nar-bundles and if so what version? Example: org.apache.nifi nifi-nar-bundles 1.2.0-SNAPSHOT It would also be helpful to see the output

Re: Pulling out hair over slf4j...

Ok thanks for all the info, I am not totally sure what is going, but I can tell you how the logging JARs are setup in NiFi and maybe that will shed some light on things... In the root pom for NiFi there is a dependencyManagement section that declares slf4j-api, jul-to-slf4j, log4j-over-slf4j, and

Pulling out hair over slf4j...

My nightmare today is a whole test suite of JUnit cases that error out with this and it only happens from JUnit tests, never from production code: I have put this in my top-level /pom.xml/ [1.7.25] but that doesn't force-feed the version to NiFi and other dependencies that have

Re: Pulling out hair over slf4j...

Bryan, Thank you very much for responding. Here's how my project is set up with Maven packaging. This is how we've been building our NAR for a year now. First, the module list. Except for /nifi-shared/, each module contains NiFi custom processors. nifi-pipeline (root, pom packaging)

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

Bryan, Thank you for putting this together. Tested on flow with a diverse set of processors. +1 binding. Only notes: - I believe the release notes should mention the change of the randomness source. While I suspect most will simply ignore, I wouldn't be surprised some people will develop

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

Andy, I opened a JIRA [1] and posted a link to the test log output [2]. I’m running Docker for Mac 17.03.1-ce-mac5 (16048) and launching the maven:latest container with `docker run -it maven:latest /bin/bash`. Event with a plain clean install (no parallelism or contrib-check) I consistently

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

Yep agreed. Can do a jira sweep based on vite thread feedback. On May 8, 2017 10:14 AM, "Andrew Psaltis" wrote: > Cool -- not sure if it is worth calling that out in next Release Guideline, > as it may trip up others or most likely myself again :) > > On Mon, May 8,

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

+1 (binding) Release this package as nifi-minifi-cpp-0.2.0 - Verified signature and hashes - Built on OSX - Successfully ran binary using provided sample config for s2s On Mon, May 8, 2017 at 2:26 AM, Koji Kawamura wrote: > +1 (non-binding) > > Full build and test

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

+0 (non-binding) -- failed building on Windows 10 using mvn clean install -Pcontrib-check -DskipTests (skipped test as build with tests failed) Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00) Maven home: c:\tools\apache-maven-3.5.0\bin\.. Java version:

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

Cool -- not sure if it is worth calling that out in next Release Guideline, as it may trip up others or most likely myself again :) On Mon, May 8, 2017 at 9:54 AM, Joe Witt wrote: > Rat check has never worked on windows and is flakey in parallel builds at > best. > > On May

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 +1 * Verified Hashes * Verified Signature * LICENSE and NOTICE appear ok (but its my first time looking at these too) * Build with - mvn -T 4C -Pcontrib-check clean install and passing * OS: Ubuntu 14.04, Oracle JDK - jdk1.8.0_77-b03 [Linux edge1

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

Rat check has never worked on windows and is flakey in parallel builds at best. On May 8, 2017 9:05 AM, "Andrew Psaltis" wrote: > +0 (non-binding) -- failed building on Windows 10 using mvn clean install > -Pcontrib-check -DskipTests (skipped test as build with tests

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

Thanks Andre. There is substantial information about the change and some discussion with the community on NIFI-3313 [1]. [1] https://issues.apache.org/jira/browse/NIFI-3313 Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP

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

If it doesn’t pass on Windows, does it make sense to add a profile trigger to avoid running the check entirely if the OS is Windows? Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On May 8, 2017, at 7:19 AM,

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

+1 (binding) - verified hashes and signature - checked over the README, LICENSE and NOTICE - build without issue on ubuntu 16.06 (x86_64) - ran a simple flow without problems On Mon, May 8, 2017 at 10:57 AM, Kevin Doran wrote: > +1 (non-binding), despite one minor bug