Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 6:36 PM Andre wrote: > +1 binding > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote: > > > All, > > > > Following a solid discussion for the past few days [1] regarding the > > establishment of Registry as a

Re: Build failure on Mac OS X with DS_STORE files

Thanks Otto, I reviewed pr1497 and merged it. For the getting started page, I assume you were referring this quick start. https://nifi.apache.org/quickstart.html I've modified the Java 8 version description as follows: "You need a recent Java 8 (or newer) JDK for the 1.x NiFi line. Older Java 8

Re: PR Builds

Joe, Perhaps we should float the following feature to the Apache INFRA folks? https://github.com/travis-ci/beta-features/issues/3 I am sure most ASF projects would incredibly benefit from travis queue deduping. Cheers On Sat, Feb 11, 2017 at 7:49 AM, Joe Witt wrote: >

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote: > All, > > Following a solid discussion for the past few days [1] regarding the > establishment of Registry as a sub-project of Apache NiFi, I'd like to > call a formal vote to record this important community

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 non-binding This will be an awesome addition. Looking forward to helping out. On Fri, Feb 10, 2017 at 17:26 u...@moosheimer.com wrote: > +1 (non-binding) > > Uwe > > > Am 10.02.2017 um 22:18 schrieb Koji Kawamura : > > > > +1 (non-binding) > >

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 (non-binding) Uwe > Am 10.02.2017 um 22:18 schrieb Koji Kawamura : > > +1 (non-binding) > > On Feb 11, 2017 5:37 AM, "Jennifer Barnabee" > wrote: > > +1 binding > > Sent from my iPhone > >> On Feb 10, 2017, at 2:55 PM, Joe Skora

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 (non-binding) On Feb 11, 2017 5:37 AM, "Jennifer Barnabee" wrote: +1 binding Sent from my iPhone > On Feb 10, 2017, at 2:55 PM, Joe Skora wrote: > > +1 binding > > On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) >

Re: PR Builds

I see the same thing on Apache Metron project ( incubating ) and we are fighting the same types of problems with travis - log size and build times etc. On February 10, 2017 at 15:49:06, Joe Witt (joe.w...@gmail.com) wrote: Otto, We get fairly sketchy results with Travis due to build

Re: PR Builds

Otto, We get fairly sketchy results with Travis due to build time/timeouts as it is a very limited infrastructure. We're evaluating ways to make that more reliable because passing PR/builds do help ease PR review. The appveyor builds are always broken at this point. But, you're PR is in and

PR Builds

Hi, I submitted my first PR today, but I’m confused about the build status. Every PR against the project looks like it is failed in some way. Is there an explanation for this?

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding Sent from my iPhone > On Feb 10, 2017, at 2:55 PM, Joe Skora wrote: > > +1 binding > > On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) > wrote: > >> +1 (non-binding) >> >> -Original Message- >> From: Bryan Bende

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) wrote: > +1 (non-binding) > > -Original Message- > From: Bryan Bende [mailto:bbe...@gmail.com] > Sent: Friday, February 10, 2017 9:41 AM > To: dev@nifi.apache.org > Subject: [VOTE] Establish Registry, a

RE: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 (non-binding) -Original Message- From: Bryan Bende [mailto:bbe...@gmail.com] Sent: Friday, February 10, 2017 9:41 AM To: dev@nifi.apache.org Subject: [VOTE] Establish Registry, a sub-project of Apache NiFi All, Following a solid discussion for the past few days [1] regarding the

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 (non-binding) On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote: > All, > > Following a solid discussion for the past few days [1] regarding the > establishment of Registry as a sub-project of Apache NiFi, I'd like to > call a formal vote to record this important

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 (non-binding) On Fri, Feb 10, 2017 at 6:26 PM, Michael Moser wrote: > It definitely sounds like careful consideration was given to the name. > > +1 (non-binding) > > > On Fri, Feb 10, 2017 at 1:03 PM, Joe Percivall > wrote: > > > Thanks for the

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

It definitely sounds like careful consideration was given to the name. +1 (non-binding) On Fri, Feb 10, 2017 at 1:03 PM, Joe Percivall wrote: > Thanks for the clarification Joe and Bryan, and we appear to be on the same > page that "Apache NiFi Registry" is how it would

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

Thanks for the clarification Joe and Bryan, and we appear to be on the same page that "Apache NiFi Registry" is how it would be referred to. With that cleared up, I am a +1. Joe On Fri, Feb 10, 2017 at 1:01 PM, Pierre Villard wrote: > +1 as well, that will be a

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 as well, that will be a very important piece of the ecosystem and looking forward its development! 2017-02-10 18:47 GMT+01:00 Joe Witt : > The name 'registry' is insufficient but we're not creating 'Apache > Registry'. We're creating a subproject of 'Apache NiFi' which is

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

The name 'registry' is insufficient but we're not creating 'Apache Registry'. We're creating a subproject of 'Apache NiFi' which is a TLP of the ASF. This subproject, just like 'MiNiFi' would properly be referred to as 'Registry: a subproject of Apache NiFi' or 'Apache NiFi Registry'. Apache

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

Well using MiNiFi as an example... Website - "MiNiFi - A subproject of Apache NiFi" Git - "nifi-minifi.git" JIRA - "Apache NiFi MiNiFi" For Registry I was thinking... Website - "Registry - A subproject of Apache NiFi" Git - "nifi-registry.git" JIRA "Apache NiFi Registry" So I didn't think

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

I 100% agree with Mike and was actually in the process of writing a very similar response. Just having "Registry" as the name will mean the trademark will be "Apache Registry" and I don't think that conveys the specificity of the sub-project. I'd much prefer something like NiFi Registry like the

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

I am in favor of the concept but the name made me pause. I did a Google search of "apache registry" and found an existing Perl module called Apache::Registry. Should I be worried about potential naming confusion? -- Mike On Fri, Feb 10, 2017 at 12:16 PM, Oleg Zhurakousky <

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 non-binding. I like the separation and I see a lot of need for this in the community. On Fri, Feb 10, 2017 at 12:03 PM, Matt Burgess wrote: > +1 binding > > On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote: > > All, > > > > Following a solid

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 Here as well. We desperately need it. > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer wrote: > > +1 non-binding. I like the separation and I see a lot of need for this in > the community. > > On Fri, Feb 10, 2017 at 12:03 PM, Matt Burgess wrote: > >>

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote: > All, > > Following a solid discussion for the past few days [1] regarding the > establishment of Registry as a sub-project of Apache NiFi, I'd like to > call a formal vote to record this important community

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 11:47 AM, Marc wrote: > +1 non-binding -- but I think creating a sub project creates a demarcation > point that separates responsibilities in a way that makes sense. > > On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 non-binding -- but I think creating a sub project creates a demarcation point that separates responsibilities in a way that makes sense. On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote: > All, > > Following a solid discussion for the past few days [1] regarding the >

[VOTE] Establish Registry, a sub-project of Apache NiFi

All, Following a solid discussion for the past few days [1] regarding the establishment of Registry as a sub-project of Apache NiFi, I'd like to call a formal vote to record this important community decision and establish consensus. The scope of this project is to define APIs for interacting

Re: Build failure on Mac OS X with DS_STORE files

https://github.com/apache/nifi/pull/1497 On February 9, 2017 at 09:19:21, Koji Kawamura (ijokaruma...@gmail.com) wrote: Thanks! Please ping me when the PR is ready. On Thu, Feb 9, 2017 at 11:15 PM, Otto Fowler wrote: > Sure - I see what you mean, that is a much better

TLS Requirements for S2S for MiNiFi

Hello Everyone, I'm seeing build failures on the head of MiNiFi-CPP on my test platform that lacks OpenSSL ( I have one with and one without ). I see that the context is defined as a member of the Site2SitePeer [1]. Clearly the Site2Site functionality works on Linux without OpenSSL, so I'm

Re: Dealing with cluster errors

Joe, External ZK quorum would be my first move. And make sure those boxes have fast disks and no heavy load from other processes. Andrew On Fri, Feb 10, 2017, 7:23 AM Joe Gresock wrote: > I should add that the flows on the individual nodes appear to be processing > the

Re: Build failure on Mac OS X with DS_STORE files

OK - I can build with the latest JDK ( except for the DS_Store issue. So the problem is that the getting started page should not just say Java 8, is should have some version of the JDK that will actually build. On February 9, 2017 at 19:34:31, Otto Fowler (ottobackwa...@gmail.com) wrote: I am

Re: Controls the order in which processors are executed

Hi Petter, It seems the image did not make it through to the list. Could you please upload it elsewhere and then provide a link? Are you looking to have a specific sequence of actions for your components? On Fri, Feb 10, 2017 at 1:24 AM, wangj...@weiresearch.com < wangj...@weiresearch.com>

Re: Dealing with cluster errors

I should add that the flows on the individual nodes appear to be processing the data just fine, and the solution I've found so far is to just wait for the data to subside, after which point the console comes up successfully. So, no complaint on the durability of the underlying data flows. It's

Dealing with cluster errors

We have a 7-node cluster and we currently use the embedded zookeepers on 3 of the nodes. I've noticed that when we have a high volume in our flow (which is causing the CPU to be hit pretty hard), I have a really hard time getting the console page to come up, as it cycles through the following