Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congratulations Jeremy. Good month for you. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Dec 20, 2016, at 03:45, Joe Witt wrote: > > Well done Jeremy and thanks for all your

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Well done Jeremy and thanks for all your contributions! On Mon, Dec 19, 2016 at 9:24 PM, Joe Percivall wrote: > Congrats Jeremy! Very well deserved. > > > - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com > > > On Monday, December 19,

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congrats Jeremy! Very well deserved.  - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com On Monday, December 19, 2016, 9:13:22 PM EST, Bryan Bende wrote:Congrats and welcome! On Mon, Dec 19, 2016 at 8:52 PM Matt Burgess

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congrats and welcome! On Mon, Dec 19, 2016 at 8:52 PM Matt Burgess wrote: Congratulations Jeremy and welcome! Very well deserved. Regards, Matt On Mon, Dec 19, 2016 at 8:23 PM, Aldrin Piri wrote: > On behalf of the Apache NiFI PMC, I am very

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congratulations Jeremy and welcome! Very well deserved. Regards, Matt On Mon, Dec 19, 2016 at 8:23 PM, Aldrin Piri wrote: > On behalf of the Apache NiFI PMC, I am very pleased to announce that Jeremy > Dyer has accepted the PMC's invitation to become a committer on the Apache

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congrats Jeremy! On Mon, Dec 19, 2016 at 8:34 PM, Tony Kurc wrote: > Congratulations and welcome, Jeremy! > > On Dec 19, 2016 8:23 PM, "Aldrin Piri" wrote: > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that > Jeremy > > Dyer has

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

Congratulations and welcome, Jeremy! On Dec 19, 2016 8:23 PM, "Aldrin Piri" wrote: > On behalf of the Apache NiFI PMC, I am very pleased to announce that Jeremy > Dyer has accepted the PMC's invitation to become a committer on the > Apache NiFi project. We greatly appreciate

[ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

On behalf of the Apache NiFI PMC, I am very pleased to announce that Jeremy Dyer has accepted the PMC's invitation to become a committer on the Apache NiFi project. We greatly appreciate all of Jeremy's hard work and generous contributions and look forward to continued involvement in the

Apache NiFi 1.1.1 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file:   https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file:   gpg --import KEYS # [optional] Clear out local

[VOTE] Release Apache NiFi 1.1.1 (RC1)

Hello Apache NiFi Community, I am pleased to be calling this vote for the source release of Apache NiFi, nifi-1.1.1. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1097 The Git tag is nifi-1.1.1-RC1 The Git

Re: OCSP validation not happening for cluster servers

Thanks, I'll check on the configuration used for the tests and reply back here once that's clear. On Mon, Dec 19, 2016 at 12:48 PM, Matt Gilman wrote: > The existing OCSP logic is part of the REST API filter chain. The > communications you're referring to are happening

Re: OCSP validation not happening for cluster servers

The existing OCSP logic is part of the REST API filter chain. The communications you're referring to are happening outside of that. Have you tried enabling OCSP as part of the SSL/TLS handshake as was mentioned in the JIRA [1]. Using the built-in features should allow us to use it throughout the

Re: OCSP validation not happening for cluster servers

Matt, It's not clients we are concerned with, but cluster servers. The test process used Java 1.8.0_65 and NiFi 0.7.1 to do the following. 1. Configure a cluster with valid certificates for each node, 2. revoke one node's certificate, 3. restart the cluster, 4. confirm with keytool

Re: OCSP validation not happening for cluster servers

Matt, I think the issue isn't going through the REST api. It's that nodes of a cluster can connect to the cluster, whether or not their certificate has been revoked. In other words, not a rogue random client, but a rouge nifi node... Brandon On Mon, Dec 19, 2016 at 11:22 AM Matt Gilman

Re: OCSP validation not happening for cluster servers

Joe, If a server connects through the REST API it should be subject to the same checks as a regular user. Can you provide more details regarding the requests that aren't being checked correctly? Additionally, there was some discussion whether we need the additional checks in the first place as

Re: OCSP validation not happening for cluster servers

This could very soon be a show stopper for us. Does anyone have any thoughts that might help us get this straight? On Wed, Dec 14, 2016 at 2:23 PM, Joe Skora wrote: > Running Apache NiFi 0.7.1, we see clients rejected due to OCSP revocation > of their certificates but we

[RESULT][VOTE] Release Apache NiFi 1.0.1

Hello The release passes with 8 +1 (binding) votes 6 +1 (non-binding) votes 0 -1 (binding) votes Thanks to all who helped make this release possible. Here is the PMC vote thread:

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1 (binding) - - - - - -  Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Monday, December 19, 2016, 9:54:04 AM EST, Mark Payne wrote: +1 ran through the build on OSX 10.10.5, Java 1.8.0_60 (Oracle), Maven 3.3.3. Verified all builds successfully

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1 ran through the build on OSX 10.10.5, Java 1.8.0_60 (Oracle), Maven 3.3.3. Verified all builds successfully and ran through some simple flows. All looks good. > On Dec 16, 2016, at 10:28 AM, Joe Percivall > wrote: > > I apologize for the improperly

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1, binding Hashes and signatures looked good Build was clean with contrib-check Ran through some simple flows On Mon, Dec 19, 2016 at 8:57 AM, Yolanda Davis wrote: > +1 (non-binding) > > Ran through release helper guide, verified signatures and hashes, then >

Re: View State error with ZK connection loss in 1.1.0

Yep, it's embedded. And yes, there's a difference.. apparently I forgot to set the Connect String in state-management.xml! Thanks for helping me catch this. Joe On Mon, Dec 19, 2016 at 2:02 PM, Bryan Bende wrote: > Hey Joe, > > Are you using embedded ZooKeeper or an

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1 (non-binding) Ran through release helper guide, verified signatures and hashes, then built and ran simple flow on OS X (java 1.8 build 111). -yolanda On Fri, Dec 16, 2016 at 10:18 AM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Hello Apache NiFi Community, > I am pleased to be

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1 (non-binding) Used Release Helper to run through steps on OSX with Java 1.8.0_112. Created and deployed few simple flows, played with templates etc., all is good. Oleg > On Dec 18, 2016, at 10:24 PM, Tony Kurc wrote: > > +1 (binding) > > Ran through helper, built on

Re: Adding JVM arguments when running NiFi...

Sounds like switching to the LinkedHashMap could address.the JVM startup flags ordering g? Andrew On Thu, Dec 15, 2016, 1:11 PM Russell Bateman wrote: > Joe, > > I have more detail and success to report... > > There is no problem in NiFi /per se/. It was not really