Re: Maven Build Failure

2018-03-25 Thread Aldrin Piri
Hmm, can't say I've seen those particular errors arise. I just made a simple Dockerfile as a sanity check that is available here: https://github.com/apiri/nifi-review-collateral/blob/master/docker-build/Dockerfile A 'docker build .' against that file is all that is needed. I ran this in a

RE: [EXT] Re: NiFi Versioned Process Group Status Icons

2018-03-25 Thread Peter Wicks (pwicks)
Matt, If you really want to enable awareness of this feature, enable the "Version" menu option even if no NiFi Registry has been enabled, and when the user clicks, "Start version control" take them to the help section for starting up a version control server and registering it. The existing

published by PublishKafkaRecord_0_10 doesn't embed schema.

2018-03-25 Thread Milan Das
Hello Nifi Users, Apparently, it seems like PublishKafkaRecord_0_10 doesn't embed schema even if it Avro Record writer is configured with “Embed Avro Schema”. I have seen the following post from Bryan Brende.  Wondering if it is a known issue or if I am missing anything here.

Re: Maven Build Failure

2018-03-25 Thread scott
Thanks for the help Aldrin. I've tried many permutations to get this to work. The two environments I've been trying to build in are Centos and Ubuntu. I've tried disabling the tests and adjusting the memory, with moderate success, but I still cannot get a complete compile. export

Re: [CANCEL][VOTE] Release Apache NiFi 1.6.0 RC1

2018-03-25 Thread Bryan Bende
I plan to review/test the fix that Sivaprasanna made first thing tomorrow morning, unless someone gets to it before then. > On Mar 25, 2018, at 10:29 AM, Joey Frazee wrote: > > Joe, yes, referring to what Bryan discovered. > > On Mar 25, 2018, 9:23 AM -0500, Joe Witt

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-25 Thread Sivaprasanna
Is it not possible to review/verify the improvements made to NIFI-4864 issue and then go ahead with the 1.6.0 release process? The new change is relatively minor so if possible, we can verify whether everything is intact and not going to introduce new problems. Maybe, if that’s the case, we can

Re: [CANCEL][VOTE] Release Apache NiFi 1.6.0 RC1

2018-03-25 Thread Joey Frazee
Joe, yes, referring to what Bryan discovered. On Mar 25, 2018, 9:23 AM -0500, Joe Witt , wrote: > Team > > RC1 vote is cancelled to correct findings of vote process. > > Joey: > I pushed the RC1 branch > https://github.com/apache/nifi/tree/NIFI-4995-RC1 as per release > guide.

[CANCEL][VOTE] Release Apache NiFi 1.6.0 RC1

2018-03-25 Thread Joe Witt
Team RC1 vote is cancelled to correct findings of vote process. Joey: I pushed the RC1 branch https://github.com/apache/nifi/tree/NIFI-4995-RC1 as per release guide. We will push the actual tag once we get to a release point. Can you clarify what fingerprint issue you are referring to? Just

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-25 Thread Joey Frazee
-1 Ran through the usual release helper stuff, but it seems like the fingerprint issue is going to cause problems, so not sure how useful putting 1.6.0 out there will be if 1.6.1 will have to be turned around immediately. Did you mean to say there's a nifi-1.6.0 -RC tag? It doesn't look like