Re: maybe a handy script for working with PRs

May I humbly suggest y'all check out the Apache Yetus project? http://yetus.apache.org/ It includes a framework for running some community decided automated tests against new contributions and works for both JIRA attachments and PRs in github.

Re: [REMINDER] Please signoff when committing other people's changes

On Thu, Mar 2, 2017 at 6:00 PM, Andre wrote: > James, > > There's no doubt the Sign-off-by is redundant (as GIT itself holds that > information, reason why GH is still able to show the information without > the sign-of-by stamp), however, I agree with your view around

Anyone interested in presenting at Data Day Texas?

See below for info about this day long conference in Austin. Anyone got something they can submit? > > -- Forwarded message -- > From: "LynnBender / GeekAustin" > Date: Sep 8, 2016 16:49 > Subject: More Speakers - and other Data Day Texas news (NLP,

[DISCUSS] Using the new 'help wanted' tool from comdev

Hi folks! ASF comdev has put up a great new tool for funneling in new folks: https://helpwanted.apache.org/ How about we brainstorm a few things here (maybe some beginner JIRAs we can flesh out a little?) and then file? -Sean

[NOTICE] jira lockdown

Hi folks! Just a quick heads-up that the ASF JIRA is currently locked down to counter a spam attack. Unfortunately, this lock down prevents our normal open-policy that allows anyone with a JIRA account to create, assign, and comment on issues. If you are caught up in this, please drop me a note

Re: [ANNOUNCE] Apache NiFi 0.6.1 release

PM, Joe Witt <joe.w...@gmail.com> wrote: > Is there some good git magic to follow to do this Sean? I could push > new signed tags? > > On Mon, Apr 18, 2016 at 11:54 PM, Sean Busbey <bus...@apache.org> wrote: >> The "rel/" prefix is part of the implement

Re: [ANNOUNCE] Apache NiFi 0.6.1 release

The "rel/" prefix is part of the implementation of an ASF policy that requires a protected immutable tag for releases. It will be present on all releases going forward and we should probably add them for our prior releases. On Mon, Apr 18, 2016 at 12:28 PM, Aldrin Piri

Re: [DISCUSS] From Contributor to Committer

Thanks for starting this Tony! As a PMC member, I really try to focus on things that help the community where we tend to have limited bandwidth: reviews weigh heavily, as does helping out new folks on users@, and doing public talking/workshops. I also am inclined to vote in favor of folks who

Re: [VOTE] Establish Apache MiNiFi, a subproject of Apache NIFi

+1 On Sat, Apr 9, 2016 at 12:13 AM, Joe Witt wrote: > Team, > > Following a solid discussion [1] in early January regarding > establishment of MiNiFi as a subproject of NiFi I'd like to call a > formal vote to record this important community decision and > established

Re: NiFi Installation : Subscribtion required

For help with vendor specific questions, please use the appropriate vendor support channel. FYI, the Hortonworks community support track that covers NiFi is: https://community.hortonworks.com/spaces/63/data-flow-track.html On Tue, Apr 5, 2016 at 4:25 AM, Aankita Kaur

Re: [DISCUSS] git branching model

On Mon, Apr 4, 2016 at 4:40 PM, Adam Lamar <adamond...@gmail.com> wrote: > On Mon, Apr 4, 2016 at 11:14 AM, Sean Busbey <bus...@apache.org> wrote: >> You're correct, a github PR only targets a single branch and Travis-CI >> only checks how the PR does at its own commit h

Re: [DISCUSS] git branching model

On Mon, Apr 4, 2016 at 1:39 PM, Tony Kurc wrote: > Sean, how about yetus? Is this something yetus can do with the patch > testing in an automated way? Right now Yetus only checks a single target branch. For commits that can apply/merge cleanly we could add something to check

Re: [DISCUSS] git branching model

You're correct, a github PR only targets a single branch and Travis-CI only checks how the PR does at its own commit hash (that is, it doesn't even check what the target branch would look like post-merge). On Mon, Apr 4, 2016 at 12:05 PM, Matt Gilman wrote: > To my

Re: Zookeeper issues mentioned in a talk about storm / heron

HBase has also had issues with ZK at modest (~couple hundred node) scale when using it to act as an intermediary for heartbeats and to do work assignment. On Thu, Mar 31, 2016 at 4:33 PM, Tony Kurc wrote: > My commentary that didn't accompany this - it appears Storm was using >

Re: EncryptContent issues after NIFI-1257 and NIFI-1259

In the mean time can we call this out in the release notes as a known issue so that folks using things as Alan was know about it before htey upgrade? On Tue, Mar 29, 2016 at 12:58 PM, Andy LoPresto wrote: > Thanks Alan. I don’t anticipate it being a large effort. I

Re: quick reminder on new nars

we could make a parent pom for all the nar modules. wanna see what that looks like? On Tue, Mar 15, 2016 at 8:46 PM, Joe Witt wrote: > Team, > > During the previous build/release cycle it was found that > javadocs/sources were being made for the Nar bundles themselves and >

Re: [VOTE] Release Apache NiFi 0.5.0 (RC3)

-1 (binding) bad: * several -source and -javadoc jars contain improper LICENSE/NOTICE files (they cover things "in the binary artifact" that are not in the artifact containing the LICENSE/NOTICE file) ex: * -source and -javadoc for war packaging * -source for nar packaging questionable: *

ApacheCon presence?

Hi folks! CFPs for ApacheCon NA Core and ApacheCon NA Big Data close in a few days, on 12 Feb. Anyone already planning to attend? Anyone already submit a proposal? I'd really like to see NiFi have a good showing. -Sean

Re: Javadoc

Hi Devin! Sorry for the gap. We're tracking the need for a web accessible copy of our API javadocs in NIFI-943. I don't believe anyone has taken up the task yet, so if you're looking to get more involved in the project we'd love the help! On Sun, Jan 17, 2016 at 1:38 PM, Devin Fisher

Re: [DISCUSS] roadmap for the next 6-12 months

On Fri, Jan 8, 2016 at 8:29 AM, Joe Witt wrote: > We should also have a discussion on how long we should be committed to > supporting the 0.x line and what that means. We need to document a > commitment for the community. Worth a dedicated thread? Presuming that we're

Re: Syslog Classes

The interface audience and stability annotations are a great idea to use. Please use the publicly-consumable ones in Apache Yetus instead of those in Hadoop. :) http://yetus.apache.org/documentation/0.1.0/audience-annotations-apidocs/ On Tue, Jan 5, 2016 at 7:34 PM, Matthew Burgess

Re: Redesign User Interface (UI)

+1 to "UI redesign warrants a major version increment" I know that we're "pre 1.0", but this sounds like it's time to figure out what we need to include to go over that cliff. On Wed, Jan 6, 2016 at 12:22 PM, Tony Kurc wrote: > Looks great so far! > > I saw the target release

Re: [DRAFT][REPORT] Apache NiFi - January 2016

On Sun, Jan 3, 2016 at 12:04 PM, Joe Witt <joew...@apache.org> wrote: > - New commmitters: > - Ricky Saltzer was added as a committer on Wed Oct 21 2015 > - Toivo Adams was added as a committer on Tue Nov 03 2015 > - Sean Busbey was added as a committer

Re: Testing handling of static class methods

You could use PowerMock to either call private static methods directly or to mock them out. https://github.com/jayway/powermock/wiki/MockStatic https://github.com/jayway/powermock/wiki/MockPrivate https://github.com/jayway/powermock/wiki/BypassEncapsulation#invoking-a-private-method On Fri,

Re: discuss nifi 0.4.1

ks > Joe > > On Fri, Dec 18, 2015 at 11:08 PM, Sean Busbey <bus...@apache.org> wrote: >> Can we update to 0.5.0 instead? The kafka client change isn't >> something I'd expect in a patch release. >> >> On Fri, Dec 18, 2015 at 9:54 PM, Joe Witt <joe.w..

Re: discuss nifi 0.4.1

d "more validation" reasoning - won't features at >>> > the end have very little validation? >>> > >>> >> On Thu, Dec 17, 2015 at 7:26 PM, Ryan Blue <b...@cloudera.com> wrote: >>> >> >>> >> Another reason to release

Re: discuss nifi 0.4.1

Sounds reasonable to me. branching off of the last release tag and then cherry picking a conservative subset of fixes for a patch release has worked well for me on another project. It's implied in your email, but just to confirm, you're only suggesting grabbing *some* of the currently-in-0.5.0

Re: discuss nifi 0.4.1

I wouldn't want to see the kafka client upgrade in a patch release. On Thu, Dec 17, 2015 at 5:37 PM, Joe Witt wrote: > OK thanks for confirming proper git fu. > > Yeah I was meaning to just grab bugs. The master branch already has stuff > that seems to warrant a minor bump

Re: discuss nifi 0.4.1

On Thu, Dec 17, 2015 at 5:50 PM, Tony Kurc wrote: > s/features/buxfixes/ > > On Thu, Dec 17, 2015 at 6:50 PM, Tony Kurc wrote: > > > Is there a reason to not just cut a 0.5.0 instead of grafting 0.5.0 > > features onto 0.4.1? > > > This is a good question.

Re: discuss nifi 0.4.1

On Thu, Dec 17, 2015 at 6:32 PM, Tony Kurc wrote: > I'm not sure I understand "more validation" reasoning - won't features at > the end have very little validation? > > On Thu, Dec 17, 2015 at 7:26 PM, Ryan Blue wrote: > > > Another reason to release 0.4.1

Re: [ANNOUNCE] New Apache NiFi Committer: Joseph (Joe) Percivall

Congrats and welcome Joe! On Mon, Dec 14, 2015 at 2:33 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Thanks Tony! > > I'm excited to continue working on such a great and innovative project. > > Joe > - - - - - - > Joseph Percivall > linkedin.com/in/Percivall > e:

Re: [VOTE] Release Apache NiFi 0.4.0 (rc2)

On Fri, Dec 11, 2015 at 8:06 AM, Sean Busbey <bus...@cloudera.com> wrote: > +1 (binding) > > * verified signatures / checksums > * source and binary artifacts passed check from RAT. > * verified source artifact against tag > * verified bin artifacts match each other and o

Re: [VOTE] Release Apache NiFi 0.4.0 (rc2)

+1 (binding) * verified signatures / checksums * source and binary artifacts passed check from RAT. * verified source artifact against tag * verified bin artifacts match each other and one generated from source artifact * spot checked licenses * build passes * bin artifact runs simple flow Ran

Re: Release wrangling: 1 week until our hopeful 0.4.0 release

sues were encountered on two different windows 8 > machines > >> by me and on windows 2012 R2 by Mark. My configuration is maven 3.3.3 > and > >> Java 1.8.0_45 (on the machine I have in front of me). > >> > > >> > Should have a patch resolv

Re: Nifi processor last execution time

Sam, For now I would store this information in HDFS. Alternatively, if you have it ZooKeeper would also work. On Thu, Nov 12, 2015 at 10:45 PM, Sam Kamau wrote: > I am working on a processor that loads data to HDFS for an RDBMS using > ExecuteSQL processor. The data has a

Re: Release wrangling: 1 week until our hopeful 0.4.0 release

Has anyone had a chance to do a pass through Feature Proposals to move out any that aren't going to make 0.4.0? https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals On Thu, Nov 12, 2015 at 8:13 AM, Tony Kurc wrote: >

Re: Avro tests are broken on Windows?

On Tue, Nov 3, 2015 at 8:58 AM, Bryan Bende wrote: > I don't really have a way of trying this since I don't have a windows > machine, but I noticed that the processor writes a new line like this: > > System.lineSeparator().getBytes(StandardCharsets.UTF_8) > > but in the test it

Re: spam to the dev mailing list

, Joe Witt <joe.w...@gmail.com> wrote: > Tony Kurc is the other moderator at this time. > > On Fri, Oct 30, 2015 at 9:58 AM, Sean Busbey <bus...@cloudera.com> wrote: >> Are the rest of the PMC already moderators? >> >> On Fri, Oct 30, 2015 at 8:19 AM, Joe Wi

Re: spam to the dev mailing list

gt; On Fri, Oct 30, 2015 at 10:02 AM, Sean Busbey <bus...@cloudera.com> wrote: > >> FWIW, the mailing list FAQ[1] says that any messages moderators don't >> respond to are treated as spam and silently dropped after 5 days. By >> actively rejecting you send a notice m

Re: [ANNOUNCE] New Apache NiFi Committer Toivo Adams

Congrats Toivo! looking forward to more great contributions! On Thu, Oct 29, 2015 at 9:16 AM, Mark Payne wrote: > All, > > On behalf of the Apache NiFI PMC, I am very pleased to announce that Toivo > Adams has accepted the PMC's invitation to become a committer on the Apache

Re: [ANNOUNCE] New Apache NiFi Committer Ricky Saltzer

Congrats Ricky! very well deserved. On Wed, Oct 21, 2015 at 2:04 PM, Tony Kurc wrote: > NiFi Community! > > Great news! > > On behalf of the Apache NiFI PMC, I am very pleased to announce that Ricky > Saltzer has accepted the PMC's invitation to become a committer on the >

Re: Newbie Dev Contribution : Questions

Oleg, Could we convince you to contribute a version of the IDE integration stuff that works within the current codebase? On Fri, Oct 16, 2015 at 5:39 AM, Venkatesh Sellappa wrote: > Thanks a bunch. > This is very good. > > I think one of the things that threw me off-course

A few questions on tracking project participation

When a jira is completed by a non-committer, who does the jira get assigned to? I couldn't find a relevant section in the contributor guide (maybe we need a "for committers" section?). If I wanted to get a sense of project activity (across committers and non-committers alike), how would I get

Re: A few questions on tracking project participation

the best link I can find is the mailing list thread the explanation references: http://search-hadoop.com/m/DHED4wHGYS On Tue, Oct 20, 2015 at 3:46 PM, Tony Kurc <trk...@gmail.com> wrote: > Sean, > I think your footnote link got chopped. > > Tony > > On Tue, Oct 20, 2015

Re: Newbie Dev Contribution : Questions

eone can add it > to the guide) > > Cheers > Oleg > > Sent from my iPhone > >> On Oct 20, 2015, at 13:07, Sean Busbey <bus...@cloudera.com> wrote: >> >> I was thinking the contributor guide, but anywhere we can add a URL to >> is fine by me. :) >&g

Re: Newbie Dev Contribution : Questions

ich could go to docs/wiki etc. Is that what > you meant? > > Cheers > Oleg > >> On Oct 20, 2015, at 3:20 PM, Sean Busbey <bus...@cloudera.com> wrote: >> >> Oleg, >> >> Could we convince you to contribute a version of the IDE integration >&g

Re: A few questions on tracking project participation

Well, I admit that my questions were as much to get more questions as to advance an idea of answers. :) On Tue, Oct 20, 2015 at 3:16 PM, Tony Kurc wrote: > Sean, > Can you better define "completed by a non-committer"? > Where the majority of the work is done by a

Re: 1.0.0 Branch Guidance

Before we make a 1.0 branch we should get consensus on what a minimally viable 1.0 release would need to contain and set a target release date (even if it's 6-9 months out). Otherwise it's too easy to end up in a situation where the 1.0 branch perpetually languishing while releases continue out

Re: What sort of major release support plan do we want to provide?

31 AM, Joe Witt <joe.w...@gmail.com> wrote: > Team, > > We should discuss an important topic that Sean Busbey raised which is > what is our plan to support major release lines. > > We should identify: > - how long to support the previous major release line(s) > - wh

Re: HDFS and Marathon

related: fuse over webhdfs: https://github.com/aw-altiscale/webhdfs On Thu, Sep 17, 2015 at 8:04 PM, Tony Kurc wrote: > has anyone tried using fuse [1] to accomplish something like what Kathy was > asking? > > [1] https://wiki.apache.org/hadoop/MountableHDFS > > On Thu, Sep 17,

Re: [DISCUSS] move nifi-assembly into top level

It's been easier, in my experience, to properly work out maven tooling to build assemblies with all of the needed legal bits via a dedicated assembly submodule rather than having it at the top level. Consider build order. The assembly should have a dependency on all the modules it includes so