Re: [EXT] [discuss] release apache nifi 1.9.0

[Joe Percivall]

 > > >>>>>>>>
> > >> > > > > > > >>>>>>>> I'd like to shoot for early next week RC
> beginning
> > if
> > >> > we can
> > >> > > > > > pull
> > >> > > > > > > >>> it
> > >> > > > > > > >>>>>> off.
> > >> > > > > > > >>>>>>>>
> > >> > > > > > > >>>>>>>> Thanks
> > >> > > > > > > >>>>>>>> Joe
> > >> > > > > > > >>>>>>>>
> > >> > > > > > > >>>>>>>> On Wed, Feb 6, 2019 at 5:07 PM Andy LoPresto <
> > >> > > > > > > >>>>>> alopresto.apa...@gmail.com  > >> > alopresto.apa...@gmail.com
> > >> > > > >>
> > >> > > > > > > >>>>>>>> wrote:
> > >> > > > > > > >>>>>>>>
> > >> > > > > > > >>>>>>>>> The PR for adding HTTP headers is complete, I
> just
> > >> > need to
> > >> > > > > > merge
> > >> > > > > > > >>>> it.
> > >> > > > > > > >>>>>> Will
> > >> > > > > > > >>>>>>>>> do today.
> > >> > > > > > > >>>>>>>>>
> > >> > > > > > > >>>>>>>>> Andy LoPresto
> > >> > > > > > > >>>>>>>>> alopre...@apache.org  alopre...@apache.org
> > >
> > >> > > > > > > >>>>>>>>> alopresto.apa...@gmail.com
> > >> > > > > > > >>>>>>>>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE
> > 3C6E
> > >> > F65B
> > >> > > > > 2F7D
> > >> > > > > > > >>> EF69
> > >> > > > > > > >>>>>>>>>
> > >> > > > > > > >>>>>>>>>> On Feb 7, 2019, at 08:23, Ed B <
> > bdes...@gmail.com
> > >> > > >  > >> > > > > > > bdes...@gmail.com>> wrote:
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>> if not too late, would be nice to have JNDI bug
> > fix
> > >> > > > included
> > >> > > > > > in
> > >> > > > > > > >>>> new
> > >> > > > > > > >>>>>>>>> release:
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>> "JMS Connection Fails After JMS servers Change
> > >> behind
> > >> > > > JNDI"
> > >> > > > > > > >>>>>>>>>>
> https://issues.apache.org/jira/browse/NIFI-5869
> > <
> > >> > > > > > > https://issues.apache.org/jira/browse/NIFI-5869>
> > >> > > > > > > >>>>>>>>>> PR is available:
> > >> > > > > > > >>>>>>>>>> https://github.com/apache/nifi/pull/3261
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>> Thank you,
> > >> > > > > > > >>>>>>>>>> Ed.
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>> On Wed, Feb 6, 2019 at 1:13 PM Joe Witt <
> > >> > > > > joe.w...@gmail.com>
> > >> > > > > > > >>>>> wrote:
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>> thanks for bumping that peter.  Mark P just
> got
> > it
> > >> > > > merged.
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>> otherwise I see a few straggling items that
> look
> > >> like
> > >> > > > they
> > >> > > > > > need
> > >> > > > > > > >>>> to
> > >> > > > > > > >>>>> be
> > >> > > > > > > >>>>>>>>>>> merged and i'll start the process!  Somehow
> this
> > >> > release
> > >> > > > > has
> > >> > > > > > > >>>>> sneakily
> > >> > > > > > > >>>>>>>>>>> become packed with good fixes and
> improvements.
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>> Thanks
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>> On Wed, Feb 6, 2019 at 10:34 AM Joe Witt <
> > >> > > > > > joe.w...@gmail.com
> > >> > > > > > > <mailto:joe.w...@gmail.com>>
> > >> > > > > > > >>>>>> wrote:
> > >> > > > > > > >>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>> agreed.  looks important enough to warrant
> > >> pulling
> > >> > in
> > >> > > > and
> > >> > > > > I
> > >> > > > > > > >>> just
> > >> > > > > > > >>>>>>>> tagged
> > >> > > > > > > >>>>>>>>>>> as
> > >> > > > > > > >>>>>>>>>>>> 1.9.0 fix version to at least force
> discussion.
> > >> > > > > > > >>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>> On Wed, Feb 6, 2019 at 10:30 AM Peter Wicks
> > >> > (pwicks) <
> > >> > > > > > > >>>>>>>>> pwi...@micron.com <mailto:pwi...@micron.com>>
> > >> > > > > > > >>>>>>>>>>>> wrote:
> > >> > > > > > > >>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> I'd like to see a review of this bug before
> we
> > >> > release
> > >> > > > > > 1.9.0,
> > >> > > > > > > >>>> as
> > >> > > > > > > >>>>> it
> > >> > > > > > > >>>>>>>>>>> helps
> > >> > > > > > > >>>>>>>>>>>>> mature the Node Offload feature.
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> NIFI-5940 Cluster Node Offload Hangs if any
> > RPG
> > >> on
> > >> > flow
> > >> > > > > is
> > >> > > > > > > >>>>> Disabled
> > >> > > > > > > >>>>>>>>>>>>> https://github.com/apache/nifi/pull/3255 <
> > >> > > > > > > https://github.com/apache/nifi/pull/3255>
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> Thanks,
> > >> > > > > > > >>>>>>>>>>>>> Peter
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> -Original Message-
> > >> > > > > > > >>>>>>>>>>>>> From: Joe Witt [mailto:joew...@apache.org]
> > >> > > > > > > >>>>>>>>>>>>> Sent: Tuesday, February 5, 2019 10:51 AM
> > >> > > > > > > >>>>>>>>>>>>> To: dev@nifi.apache.org
> > >> > > > > > > >>>>>>>>>>>>> Subject: [EXT] [discuss] release apache nifi
> > >> 1.9.0
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> Team,
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>
> > >> > > > > > > >>>>>>>>
> > >> > > > > > > >>>>>>
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> >
> > >>
> >
> https://issues.apache.org/jira/browse/NIFI-5995?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Resolved%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.9.0%20ORDER%20BY%20key%20DESC
> > >> > > > > > > <
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> >
> > >>
> >
> https://issues.apache.org/jira/browse/NIFI-5995?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Resolved%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.9.0%20ORDER%20BY%20key%20DESC
> > >> > > > > > > >
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> We have a pretty large list of bugs/features
> > >> added
> > >> > > > > already
> > >> > > > > > to
> > >> > > > > > > >>>>>>>> justify
> > >> > > > > > > >>>>>>>>> a
> > >> > > > > > > >>>>>>>>>>>>> 1.9.0 release as well.
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> I'm happy to give RM a go again unless there
> > are
> > >> > > > > volunteers
> > >> > > > > > > >>>>>> strongly
> > >> > > > > > > >>>>>>>>>>>>> interested.
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>> Thanks
> > >> > > > > > > >>>>>>>>>>>>> Joe
> > >> > > > > > > >>>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>>
> > >> > > > > > > >>>>>>>>>> --
> > >> > > > > > > >>>>>>>>>> Edward Berezitsky
> > >> > > > > > > >>>>>>>>>> bdes...@gmail.com
> > >> > > > > > > >>>>>>>>>
> > >> > > > > > > >>>>>>>>
> > >> > > > > > > >>>>>>>
> > >> > > > > > > >>>>>>>
> > >> > > > > > > >>>>>>> --
> > >> > > > > > > >>>>>>> Edward Berezitsky
> > >> > > > > > > >>>>>>> bdes...@gmail.com
> > >> > > > > > > >>>>>>
> > >> > > > > > > >>>>>>
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> >
> > >>
> > >
> >
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Improve S2S to ease "star deployments"

[Joe Percivall]

time. Site-to-Site was
> > > added for convenience so that users could just point to a given URL and
> > be
> > > provided the list of available ports and have it
> > > auto-load balance across the cluster (if applicable). But in your use
> > > case, neither of these really benefit you because you don't
> > > know the URL to send to a priori and you already know exactly which
> node
> > > to push to.
> > >
> > > Thanks
> > > -Mark
> > >
> > >
> > >
> > >
> > > > On Sep 15, 2018, at 9:05 AM, Pierre Villard <
> > pierre.villard...@gmail.com>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Here is my use case: I've multiple NiFi standalone instances deployed
> > > over
> > > > multiple sites (that could be MiNiFi instances) and a central NiFi
> > > > cluster.  The standalone instances generate data, the data is sent to
> > the
> > > > central cluster to be parsed and enriched before being sent back to
> the
> > > > standalone instances. The data needs to go back where it's been
> > > generated.
> > > >
> > > > At the moment, since RPG cannot be configured using EL and FFs
> > > attributes,
> > > > you need to have one port (or one RPG if the RPG is on central NiFi's
> > > side)
> > > > per standalone instance. And I don't think that changing the RPG to
> > > handle
> > > > FFs attributes scope would be a good idea in terms of implementation.
> > > >
> > > > Instead I'd like to change the S2S protocol to allow RPG pulling
> based
> > on
> > > > FFs attributes.
> > > >
> > > > On the standalone instances, we would have:
> > > > Workflow generating data => RPG => workflow receiving enriched data
> > from
> > > > central cluster
> > > >
> > > > On the NiFi cluster, we would have:
> > > > input port => workflow parsing and enriching data => output port
> > > >
> > > > The idea would be that, when configuring an output port in the RPG,
> > it'd
> > > be
> > > > possible to enable "host based pulling" so that only flow files
> having
> > > the
> > > > attribute 's2s.host' matching the host of the instance hosting the
> RPG
> > > > would be pulled. (the s2s.port attribute is already set when data is
> > sent
> > > > through S2S).
> > > >
> > > > I already started working on that approach and even though I don't
> have
> > > > something fully functional yet, I wanted to discuss it here to be
> sure
> > > this
> > > > would be interesting for the wider community and, also, if I'm not
> > > missing
> > > > something obvious that would prevent it.
> > > >
> > > > Happy to file a JIRA if that sounds interesting.
> > > >
> > > > Thanks,
> > > > Pierre
> > >
> > >
> >
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Status of "event-driven" scheduling

[Joe Percivall]

uessing here, but I think the Event Driven scheduling was intended
> to
> > be more efficient than Timer Driven scheduling, in the way that push
> > notifications should be more efficient than polling.  In practice, I'm
> not
> > sure anyone has measured the difference.
> >
> > I have seen folks use Event Driven scheduling to get access to the
> separate
> > thread pool from the Timer Driven pool.  For example, if you are running
> on
> > an 8 core system but you want a Timer Driven pool with 50 threads to do
> > lots of I/O bound tasks, you might create an Event Driven pool with 4
> > threads and assign your CPU heavy processing to that pool.  This limit
> may
> > avoid having way more than 8 CPU heavy threads (from the Timer Driven
> pool)
> > bogging down your 8 core system.
> >
> > Regards,
> > -- Mike
> >
> >
> > On Thu, Sep 6, 2018 at 3:11 PM Joe Percivall 
> wrote:
> >
> >> Hey everyone,
> >>
> >> The dataflow I'm running has one main flow and a couple other disjoint
> >> process groups. Within that main flow, there are sections which aren't
> used
> >> very often. In trying to optimize things, I looked into the guidance we
> >> have on the "event-driven" scheduling type. There doesn't appear to be
> much
> >> concrete other than "it's experimental". Which has been the go-to,
> >> basically since being open-sourced.
> >>
> >> So with that, I'm curious about a couple things:
> >> 1: With the recent improvements to the controller and timer-based
> >> scheduling, what should be our guidance on when to use event-based over
> >> timer-based?
> >> 2: Is anyone actually using it in production?
> >> 3: Given it's been 3+ years of "it's experimental", we should start
> >> thinking about either declaring it good to go or deprecating it.
> >> 4: Any lessons learned on optimizing disjoint/sparse flows.
> >>
> >> Cheers,
> >> Joe
> >> --
> >> *Joe Percivall*
> >> linkedin.com/in/Percivall
> >> e: jperciv...@apache.com
> >>
>
>

-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Status of "event-driven" scheduling

[Joe Percivall]

Hey everyone,

The dataflow I'm running has one main flow and a couple other disjoint
process groups. Within that main flow, there are sections which aren't used
very often. In trying to optimize things, I looked into the guidance we
have on the "event-driven" scheduling type. There doesn't appear to be much
concrete other than "it's experimental". Which has been the go-to,
basically since being open-sourced.

So with that, I'm curious about a couple things:
1: With the recent improvements to the controller and timer-based
scheduling, what should be our guidance on when to use event-based over
timer-based?
2: Is anyone actually using it in production?
3: Given it's been 3+ years of "it's experimental", we should start
thinking about either declaring it good to go or deprecating it.
4: Any lessons learned on optimizing disjoint/sparse flows.

Cheers,
Joe
-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: InvokeHttp-1.6.0

[Joe Percivall]

Hello Vinod,

The underlying library for InvokeHttp that we use to make the HTTP calls,
OkHttp, removed these with their 3.1.0 release[1]. They were considered a
"leaked implementation detail". There appears to be a workaround but that'd
be a not insignificant amount of work to implement. You're more than
welcome to create a ticket for implementation though.

[1] https://github.com/square/okhttp/issues/2035

Joe

On Sat, Apr 21, 2018 at 2:03 AM, vinod rapolu <rapoluvi...@gmail.com> wrote:

> Hi Team,
>
>
> In InvokeHttp-1.0.0 processor I have response attributes as "
> *OkHttp-Received-Millis,OkHttp-Sent-Millis "*
>
>   I am not able to find those attributes in invokehttp-1.6.0.
>
> Please Help me to get those attributes in version 1.6.0 also*.*
> --
> With Regards,
>
> Vinod Kumar Rapolu.
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Rat errors building with mvn clean install -Pcontrib-check

[Joe Percivall]

Hey Otto,

I've run into this before and it's typically due to switching between
branches where modules have been added/removed. If you look at the files
it's complaining about they're all in a target folder. Those are typically
ignored when the maven module is included (i.e. the nifi-hadoop-utils
module). When you switch off of a branch that had that, the ignored files
stick around (i.e. the target folder).

Long story short, you didn't do anything wrong. Just a by-product of doing
dev work and you just need to remove the offending files.

Joe

On Tue, Mar 27, 2018 at 11:02 AM, Otto Fowler <ottobackwa...@gmail.com>
wrote:

> I have a branch on my work where I have been doing processor work.
> I ran mvn clean install -Pcontrib-check
> and now I’m getting rat errors for nifi-commons, which I didn’t change at
> all.  As anyone see this?
>
> *
> Summary
> ---
> Generated at: 2018-03-27T10:56:27-04:00
>
> Notes: 18
> Binaries: 44
> Archives: 2
> Standards: 18
>
> Apache Licensed: 1
> Generated Documents: 0
>
> JavaDocs are generated, thus a license header is optional.
> Generated files do not require license headers.
>
> 15 Unknown Licenses
>
> *
>
> Files with unapproved licenses:
>
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/test-classes/krb5.conf
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/testCompile/
> groovy-tests/inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/testCompile/
> groovy-tests/createdFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/
> inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/
> createdFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/compile/
> default-compile/inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/maven-status/maven-compiler-plugin/compile/
> default-compile/createdFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/surefire-reports/org.apache.nifi.hadoop.TestKerberosProperties.txt
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/surefire-reports/TEST-org.apache.nifi.hadoop.
> TestKerberosProperties.xml
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-hadoop-utils/
> target/.plxarc
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-processor-
> utilities/target/maven-status/maven-compiler-plugin/
> testCompile/groovy-tests/inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-processor-
> utilities/target/maven-status/maven-compiler-plugin/testCompile/default-
> testCompile/inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-processor-
> utilities/target/maven-status/maven-compiler-plugin/compile/
> default-compile/inputFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-processor-
> utilities/target/maven-status/maven-compiler-plugin/compile/
> default-compile/createdFiles.lst
>
> /Users/ottobackwards/src/apache/forks/nifi/nifi-commons/nifi-processor-
> utilities/target/.plxarc
>
> *
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Maven Build Failure

[Joe Percivall]

I ran into the second error today after wiping my m2 directory and running
a parallel build skipping tests. Looking at the maven pom, I believe it is
because "nifi-slack-processors" has a test dependency on
"nifi-standard-processors".
If you build the "nifi-standard-processors" first, it should fix the error.

Joe

On Sun, Mar 25, 2018 at 10:32 PM, Aldrin Piri <aldrinp...@gmail.com> wrote:

> 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 couple environments successfully inclusive of an older
> laptop with Centos 7 and, the other, a more modern desktop running Debian
> 9.  Could you let us know if this is also problematic?
>
> Thanks!
>
> --Aldrin
>
> On Sun, Mar 25, 2018 at 2:02 PM, scott <tcots8...@gmail.com> wrote:
>
> > 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 MAVEN_OPTS="-Xms2G -Xmx8G"
> > mvn clean install  -Dmaven.test.skip=true
> >
> > Env1:
> > Centos 7, Apache Maven 3.5.3, Open JDK 64bit 1.8.0_161
> > Farthest I've gotten is nifi-web-ui
> > [ERROR] Failed to extract goal com.github.eirslett:frontend-m
> > aven-plugin:1.1:install-node-and-npm (install-node-and-npm) on project
> > nifi-web-ui: Could not extract the Node archive:
> > '/home/scotty/.m2/repository/com/github/eirslett/node/5.7.
> 0/node-5.7.0-linux-x64.tar.gz':
> > Operation not permitted
> >
> > Env2:
> > Ubuntu 16.04 LTS, Apache Maven 3.3.9, Open JDK 64 bit 1.8.0_151
> > Farthest I've gotten is nifi-slack-processors
> > [ERROR] Failed to execute goal on project nifi-slack-processors: Could
> not
> > resolve dependencies for project org.apache.nifi:nifi-slack-
> processors:jar:1.6.0-SNAPSHOT:
> > Could not find artifact org.apache.nifi:nifi-standard-
> > processors:jar:tests:1.6.0-SNAPSHOT in apache.snapshots (
> > https://repository.apache.org/snapshots)
> >
> > Thanks,
> > Scott
> >
> >
> >
> > On 03/24/2018 07:14 PM, Aldrin Piri wrote:
> >
> >> Hi Scott,
> >>
> >> Are the issues with tests or something else?  Could you share the
> error(s)
> >> you are seeing during the build process?  I just checked out Travis, and
> >> it
> >> looks like we are building normally.
> >>
> >>
> >> Could you share more about your environment?
> >>
> >> "mvn -version" would be a great start as well as letting us know what
> >> distributions you attempted the build.
> >>
> >> Hopefully we can smooth out whatever is amiss and get you to those
> custom
> >> processors.
> >>
> >> --aldrin
> >>
> >>
> >> On Sat, Mar 24, 2018 at 9:41 PM, scott <tcots8...@gmail.com> wrote:
> >>
> >> Hello Devs,
> >>>
> >>> I've been struggling with building NiFi's latest version. I've tried
> >>> turning off the tests, building on two different Linux instances and
> >>> different versions of Maven and Java and even gave it more memory. It
> >>> always stops somewhere in the build before completing. I'm just
> wondering
> >>> if there is a secret handshake I'm missing. Is there a docker base
> image,
> >>> for instance, that has an environment that will build NiFi every time?
> It
> >>> takes a while to build/fail, so I'm just a bit frustrated. I'm not
> really
> >>> interested in becoming a Maven expert, just want to crank out some
> custom
> >>> processors.
> >>>
> >>> Thanks for your time,
> >>>
> >>> Scott
> >>>
> >>>
> >>>
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi Committer Mike Thomsen

[Joe Percivall]

Thank you for your prior and continued contributions Mike, and congrats!

On Wed, Mar 21, 2018 at 12:59 PM, Marco Gaido <marcogaid...@gmail.com>
wrote:

> Congrats Mike! Well deserved!
>
> On Wed, 21 Mar 2018, 16:53 Sivaprasanna, <sivaprasanna...@gmail.com>
> wrote:
>
> > Congratulations, Mike :)
> >
> > On Wed, 21 Mar 2018 at 8:57 PM, Jeff <jtsw...@gmail.com> wrote:
> >
> > > Congrats Mike!
> > >
> > > On Wed, Mar 21, 2018 at 11:20 AM Scott Aslan <scottyas...@gmail.com>
> > > wrote:
> > >
> > > > Congrats!
> > > >
> > > > On Wed, Mar 21, 2018 at 10:15 AM, Pierre Villard <
> > > > pierre.villard...@gmail.com> wrote:
> > > >
> > > > > Congrats Mike, well deserved!
> > > > >
> > > > > 2018-03-21 14:55 GMT+01:00 Mike Thomsen <mikerthom...@gmail.com>:
> > > > >
> > > > > > Thanks everyone!
> > > > > >
> > > > > > On Wed, Mar 21, 2018 at 9:55 AM, Joe Witt <joe.w...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > Mike
> > > > > > >
> > > > > > > Thanks for all the great contributions and reviews and
> > discussions
> > > > and
> > > > > > > congratulations on the well deserved commit bit!
> > > > > > >
> > > > > > > Thanks
> > > > > > > Joe
> > > > > > >
> > > > > > > On Wed, Mar 21, 2018 at 1:53 PM, Kevin Doran <
> kdo...@apache.org>
> > > > > wrote:
> > > > > > > > Congrats, Mike!
> > > > > > > >
> > > > > > > > On 3/21/18, 09:42, "Tony Kurc" <tk...@apache.org> wrote:
> > > > > > > >
> > > > > > > > On behalf of the Apache NiFI PMC, I am very pleased to
> > > announce
> > > > > > that
> > > > > > > Mike
> > > > > > > > has accepted the PMC's invitation to become a committer
> on
> > > the
> > > > > > > Apache NiFi
> > > > > > > > project. We greatly appreciate all of Mike's hard work
> and
> > > > > generous
> > > > > > > > contributions to the project. We look forward to his
> > > continued
> > > > > > > involvement
> > > > > > > > in the project.
> > > > > > > >
> > > > > > > > Mike has been contributing to the project for quite a
> > while,
> > > > > > > contributing
> > > > > > > > features such as  enhancements to MongoDB and HBase
> > > processors
> > > > as
> > > > > > > well as
> > > > > > > > things like improvements to Expression Language and
> > > > > LookupService.
> > > > > > > I'm sure
> > > > > > > > many of you have interacted with Mike on the mailing
> lists
> > > > where
> > > > > he
> > > > > > > has
> > > > > > > > been giving great input on both the project and
> community.
> > We
> > > > > also
> > > > > > > > appreciate his work reviewing and providing feedback on
> new
> > > > > > > contributions.
> > > > > > > >
> > > > > > > > Welcome and congratulations!
> > > > > > > > Tony
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [VOTE] Establish Fluid Design System, a sub-project of Apache NiFi

[Joe Percivall]

+ 1

On Sat, Mar 10, 2018 at 6:29 PM, Rob Moran <rmo...@gmail.com> wrote:

> +1
>
> On Sat, Mar 10, 2018, 12:59 PM James Wing <jvw...@gmail.com> wrote:
>
> > +1
> >
> > On Fri, Mar 9, 2018 at 12:10 PM, Scott Aslan <scottyas...@gmail.com>
> > wrote:
> >
> > > All,
> > >
> > > Following a solid discussion for the past couple of weeks [1] regarding
> > the
> > > establishment of Fluid Design System 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 a theme-able set of high quality
> > UI
> > > components and utilities for use across the various Apache NiFi web
> > > applications in order to provide a more consistent user experience.
> > >
> > > I am a +1 and looking forward to the future work in this area.
> > >
> > > The vote will be open for 72 hours and be a majority rule vote.
> > >
> > > [ ] +1 Establish Fluid Design System, a subproject of Apache NiFi
> > > [ ]   0 Do not care
> > > [ ]  -1 Do not establish Fluid Design System, a subproject of Apache
> NiFi
> > >
> > > Thanks,
> > >
> > > ScottyA
> > >
> > > [1] *http://mail-archives.apache.org/mod_mbox/nifi-dev/201802.mbox/%
> > > 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com
> > %3E
> > > <http://mail-archives.apache.org/mod_mbox/nifi-dev/201802.mbox/%
> > > 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com
> > %3E
> > > >*
> > >
> >
> --
> Rob
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

[Joe Percivall]

Scott,

Definitely like the direction of standardizing NiFi and Registry around the
same set of components, so the user has a common UX. Is there precedent for
creating a new sub-project just for common components/modules to be used by
the top-level, and it's other sub-projects? My concerns are similar to
Joe's. Along those lines, if the core problems we're trying to address is
the release process and distribution, is there a less "heavy-weight" avenue?

In the past, we've also talked about pulling out the core NiFi framework to
be shared between NiFi and MiNiFi-Java for similar reasons. How we go about
solving this for the UI could be used a model for the core framework as
well.

- Joe

On Thu, Feb 22, 2018 at 10:58 AM, Mike Thomsen <mikerthom...@gmail.com>
wrote:

> Also, what sort of framework is the UI being standardized on? Angular?
> React? Something else?
>
> On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt <joe.w...@gmail.com> wrote:
>
> > Scott
> >
> > Ok so extract out the fluid design work you started with NiFi Registry
> > to its own codebase which can be rev'd and published to NPM making it
> > easier to consume/reuse across NiFi projects and offers better
> > consistency.  This sounds interesting.
> >
> > In thinking through the additional community effort or the effort
> > trade-off:
> > How often do you anticipate we'd be doing releases (and thus
> > validation/voting) for this?
> > How often would those differ from when we'd want to do a NiFi or NiFi
> > Registry release?
> > How do you envision the community would be able to help vet/validate
> > releases of these modules?
> >
> > Thanks
> > Joe
> >
> > On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan <scottyas...@gmail.com>
> > wrote:
> > > NiFi Community,
> > >
> > > I'd like to initiate a discussion around creating a sub-project of NiFi
> > to
> > > encompass the Fluid Design System NgModule created during the
> development
> > > of the NiFi Registry. A possible name for this sub-project is simply
> > > "NiFi Fluid
> > > Design System". The idea would be to create a sub-project that
> > distributes
> > > an atomic set of high quality, reuse-able, theme-able, and testable
> UI/UX
> > > components, fonts, and other JS modules for use across the various web
> > > applications throughout the NiFi universe (uNiFiverse???). Both NiFi
> and
> > > NiFi Registry web applications would eventually leverage this module
> via
> > > npm. This approach will enable us to provide our users with a
> consistent
> > > experience across web applications. Creating a sub-project would also
> > allow
> > > the FDS code to evolve independently of NiFi/NiFi registry and be
> > released
> > > on it's own timeline. In addition, it would make tracking issues/work
> > much
> > > clearer through a separate JIRA.
> > >
> > > Please discuss and provide and thoughts or feedback.
> > >
> > > Thanks,
> > >
> > > Scotty
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Empty String in UpdateAttribute

[Joe Percivall]

Hey Mark,

Yeah, at the time I couldn't think of a use-case that a user would want to
set an attribute to empty so when I added the validator for the stateful
portion, I added the empty validator as well. That said, I don't see a need
to keep it if it's preventing your use-case. Curious, what is your use-case
that you always need to set an attribute to an empty string?

- Joe



On Fri, Jan 19, 2018 at 2:43 PM, Michael Moser <moser...@gmail.com> wrote:

> Hi Mark,
>
> After reading the JIRA [1] and the PR for the UpdateAttribute
> modifications, I believe this was simply an unintended consequence of the
> code changes.  If you would like to write a new JIRA, then I'm sure we can
> restore the "Set Empty String" functionality when not storing attributes in
> local state.
>
> [1] - https://issues.apache.org/jira/browse/NIFI-1582
>
> -- Mike
>
>
> On Thu, Jan 18, 2018 at 5:11 PM, Mark Bean <mark.o.b...@gmail.com> wrote:
>
> > UpdateAttribute supports stateful properties. In doing so, the validator
> > applied to the attributes changes. In the case where stateful properties
> > are not desired, the validator adds StandardValidators.NON_EMPTY_
> > VALIDATOR.
> > This means the "Set Empty String" checkbox cannot be used.
> >
> > One solution is to store state locally, and then set both the Stateful
> > Variables Initial Value and the dynamic property to the Empty String.
> >
> > However, my question: why is the NON_EMPTY_VALIDATOR added (when stateful
> > is not set) versus just the ATTRIBUTE_KEY_PROPERTY_NAME_VALIDATOR?
> >
> > Thanks,
> > Mark
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0 - RC3

[Joe Percivall]

+1 (binding)

Ran a clean build and contrib check. Looked over the hashes, and the L
and README. Utilized the toolkit, ran a simple S2S flow and checked the
status from the command line. All worked as expected.



On Wed, Dec 20, 2017 at 3:19 PM, Joe Witt <joe.w...@gmail.com> wrote:

> +1 (binding)
>
> Build/clean contrib check/L review. Sigs/etc.. all check out.
>
> Ran into this issue https://issues.apache.org/jira/browse/MINIFI-421
>
>
>
> On Wed, Dec 20, 2017 at 12:03 PM, Marc <phroc...@apache.org> wrote:
> > +1 -- binding to release minifi-0.3.0
> >
> > verified hashes and sigs
> > successful build w/ contrib-check
> > ran some MiNiFi -> NiFi flows I use for testing.
> >
> > Looks great!
> >
> > On Tue, Dec 19, 2017 at 8:59 AM, Pierre Villard <
> pierre.villard...@gmail.com
> >> wrote:
> >
> >> +1 - binding - release this package as minifi-0.3.0
> >>
> >> Went through the release helper guide. Executed some workflows MiNiFi ->
> >> NiFi. All good.
> >>
> >> Thanks to everyone involved in this release!
> >>
> >>
> >> 2017-12-19 14:47 GMT+01:00 Jeff Zemerick <jzemer...@apache.org>:
> >>
> >> > +1 non-binding
> >> >
> >> > verified hashes
> >> > verified signature
> >> > verified git commit
> >> > verified RC branch commit
> >> > successful build with contrib-check
> >> > verified the three sets of README, LICENSE, NOTICE files
> >> > verified windows service operation
> >> >
> >> > Thanks for putting these RCs together!
> >> >
> >> > Jeff
> >> >
> >> >
> >> > On Tue, Dec 19, 2017 at 12:51 AM, Koji Kawamura <
> ijokaruma...@gmail.com>
> >> > wrote:
> >> >
> >> > > Thanks Aldrin for updating RC again, and to all devs who contributed
> >> > > to MiNiFi 0.3.0 release!
> >> > >
> >> > > I confirmed:
> >> > > - Hashes are correct
> >> > > - MiNiFi Windows Service works
> >> > > - MiNiFi Toolset works, NiFi template -> MiNiFi config yml
> >> > > - NiFi template -> C2 server -> MiNiFi PullHttpChangeIngestor works
> >> > nicely
> >> > >
> >> > > +1 Release this package as minifi-0.3.0
> >> > >
> >> > > Koji
> >> > >
> >> > > On Tue, Dec 19, 2017 at 7:09 AM, Aldrin Piri <ald...@apache.org>
> >> wrote:
> >> > > > Hello,
> >> > > >
> >> > > > I am pleased to call this vote for the source release of Apache
> NiFi
> >> > > MiNiFi,
> >> > > > minifi-0.3.0.
> >> > > >
> >> > > > The source zip, including signatures, digests, etc. can be found
> at:
> >> > > > https://repository.apache.org/content/repositories/
> >> orgapachenifi-1114/
> >> > > >
> >> > > > The Git tag is minifi-0.3.0-RC3
> >> > > > The Git commit ID is f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> >> > > > *
> >> > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=
> >> commit;h=
> >> > > f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> >> > > > *
> >> > > > https://github.com/apache/nifi-minifi/commit/
> >> > > f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> >> > > >
> >> > > > Checksums of minifi-0.3.0-source-release.zip:
> >> > > > MD5: 685e890486dbde4fd75db86128adf140
> >> > > > SHA1: 9dcf7d1b440b1247ca0c55e2ffdc75574467fed6
> >> > > > SHA256: a1c9be5ca4824fe98620d7df68469c
> 8b9ea9461fb8dbecd1bdd6596e0b5d
> >> > ea89
> >> > > > Release artifacts are signed with the following key:
> >> > > > https://people.apache.org/keys/committer/aldrin.asc
> >> > > >
> >> > > > KEYS file available here:
> >> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >> > > >
> >> > > > 23 issues were closed/resolved for this release:
> >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > > projectId=12319921=12340598
> >> > > >
> >> > > > Release note highlights can be found here:
> >> > > > https://cwiki.apache.org/confluence/display/MINIFI/
> >> > > Release+Notes#ReleaseNotes-Version0.3.0
> >> > > >
> >> > > > The vote will be open until 7:00PM EST, 21 December 2017 [1].
> >> > > >
> >> > > > Please download the release candidate and evaluate the necessary
> >> items
> >> > > > including checking hashes, signatures, build
> >> > > > from source, and test.  Then please vote:
> >> > > >
> >> > > > [ ] +1 Release this package as minifi-0.3.0
> >> > > > [ ] +0 no opinion
> >> > > > [ ] -1 Do not release this package because...
> >> > > >
> >> > > > Thanks!
> >> > > >
> >> > > > [1] You can determine this time for your local time zone at
> >> > > > https://s.apache.org/minifi-0.3.0-rc3-close
> >> > >
> >> >
> >>
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0

[Joe Percivall]

There are some really cool new features in this release and I'm really
looking forward to seeing NiFi + MiNiFi + Registry all working together.
Thanks everyone for their hard work!

I was able to verify the hashes and the normal build + contrib check work
on OSX 10.12.5. Also, a simple S2S flow communicating to NiFi 1.4.0 works
as expected. Unfortunately, I am continually hitting MINIFI-416[1] when
running the tests in minifi-integration-tests (either using the command
line or IDE). I believe the cause of which is the switch to Alpine Linux as
the base docker image. That said, I'd like to get verification that this
isn't just a configuration issue on my end before voting "-1".

Also, I was surprised we haven't upgraded past NiFi-1.2.0 yet. I went ahead
and created a ticket for it[2] and put up a PR[3]. Not something that needs
to be in the release, I just wanted to bring attention to it.

[1] https://issues.apache.org/jira/browse/MINIFI-416
[2] https://issues.apache.org/jira/browse/MINIFI-417
[3] https://github.com/apache/nifi-minifi/pull/103

Joe

On Sun, Dec 10, 2017 at 6:42 PM, Aldrin Piri <ald...@apache.org> wrote:

> Hello,
>
> I am pleased to call this vote for the source release of Apache NiFi
> MiNiFi, minifi-0.3.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1112
>
> The Git tag is minifi-0.3.0-RC1
> The Git commit ID is 930c3fb0112c043614158018d0d8f1ca31a4f1d8
> * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=
> commit;h=930c3fb0112c043614158018d0d8f1ca31a4f1d8
> * https://github.com/apache/nifi-minifi/commit/930c3fb0112c043
> 614158018d0d8f1ca31a4f1d8
>
> Checksums of minifi-0.3.0-source-release.zip:
> MD5:  69f2e8b90af7a7bdec45684406c7b83d
> SHA1:  bc0e8e1edb13f9f6ea69f19cfb70d18443b6604f
> SHA256:  b11c6df7c82479d77c4c245cfb737fe15cb2bd4742c962b08375485bbbe2894e
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/aldrin.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 18 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12319921=12340598
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/MINIFI/Release+N
> otes#ReleaseNotes-Version0.3.0
>
> The vote will be open for at 72 hours and close at 7:30PM EDT, 13 December
> 2017 [1].
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  Then please vote:
>
> [ ] +1 Release this package as minifi-0.3.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
>
> [1] You can determine this time for your local time zone at
> https://s.apache.org/minifi-0.3.0-rc1-close
>
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

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

[Joe Percivall]

sing
> >> > > -DskipTests works.
> >> > > Ran some simple flows that worked as expected.
> >> > >
> >> > > Many thanks to the community for all of the work put into this
> >> > > release!  And thanks to Jeff for being RM.
> >> > >
> >> > >
> >> > > On Fri, Sep 29, 2017 at 4:44 PM, Scott Aslan <scottyas...@gmail.com
> >
> >> > wrote:
> >> > >
> >> > > +1 (non-binding) Release this package as nifi-1.4.0
> >> > >
> >> > > On Fri, Sep 29, 2017 at 11:52 AM, Mark Payne <marka...@hotmail.com>
> >> > wrote:
> >> > >
> >> > > +1 (binding)
> >> > >
> >> > > Verified hashes and checksum. Built with all unit tests and
> >> contrib-check
> >> > > on OSX.
> >> > >
> >> > > Was able to startup and test simple flows worked as expected.
> >> > >
> >> > > On Sep 29, 2017, at 11:20 AM, Marc P. <marc.par...@gmail.com>
> wrote:
> >> > >
> >> > > +1 non-binding
> >> > >
> >> > > -- verified contrib-check
> >> > > -- ran simple flows with MiNiFi
> >> > > -- sigs and hashes look good.
> >> > >
> >> > > Thanks for sending this out Jeff!
> >> > >
> >> > >
> >> > > On Fri, Sep 29, 2017 at 11:18 AM, Matt Gilman <
> matt.c.gil...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > +1 (binding) Release this package as nifi-1.4.0
> >> > >
> >> > > On Fri, Sep 29, 2017 at 11:07 AM, Bryan Bende <bbe...@gmail.com>
> >> wrote:
> >> > >
> >> > > +1 (binding)
> >> > >
> >> > > - Ran through the release helper and everything checked out.
> >> > > - Ran a couple of sample flows with no issues
> >> > >
> >> > >
> >> > > On Fri, Sep 29, 2017 at 9:46 AM, James Wing <jvw...@gmail.com>
> wrote:
> >> > >
> >> > > Jeff, I agree the updated KEYS file has been published.  Thanks.
> >> > >
> >> > > On Fri, Sep 29, 2017 at 6:00 AM, Jeff <jtsw...@gmail.com> wrote:
> >> > >
> >> > > James,
> >> > >
> >> > > I had to do a hard reload of the page in Chrome, since the browser
> >> > >
> >> > > kept
> >> > >
> >> > > showing me a cached version without my key.  After the hard reload,
> I
> >> > >
> >> > > can
> >> > >
> >> > > see my key at https://dist.apache.org/repos/dist/dev/nifi/KEYS.
> >> > >
> >> > > Could
> >> > >
> >> > > you
> >> > >
> >> > > try opening the KEYS link in incognito mode and verify that my key
> is
> >> > > there?
> >> > >
> >> > > Thanks,
> >> > > Jeff
> >> > >
> >> > > On Fri, Sep 29, 2017 at 1:06 AM James Wing <jvw...@gmail.com>
> wrote:
> >> > >
> >> > > +1 (binding). I ran through the release helper including signature,
> >> > >
> >> > > hashes,
> >> > >
> >> > > build, and testing the binary.  I checked the LICENSE and NOTICE
> >> > >
> >> > > files.
> >> > >
> >> > > Everything looks good to me.
> >> > >
> >> > > One thing I noted is that Jeff's GPG key is not yet in the public
> >> > >
> >> > > KEYS
> >> > >
> >> > > file
> >> > >
> >> > > at https://dist.apache.org/repos/dist/dev/nifi/KEYS, but it is
> >> > >
> >> > > added
> >> > >
> >> > > in
> >> > >
> >> > > the
> >> > > master branch KEYS file to be published with the release.  I believe
> >> > >
> >> > > that
> >> > >
> >> > > is OK for the signature, we've done this before, and perhaps we
> >> > >
> >> > > should
> >> > >
> >> > > consider changing the helper text in the future.
> >> > >
> >> > > Thanks, Jeff, for putting this release together.
> >> > >
> >> > >
> >> > > On Thu, Sep 28, 2017 at 12:54 PM, Jeff <jsto...@apache.org> wrote:
> >> > >
> >> > > Hello,
> >> > >
> >> > > I am pleased to be calling this vote for the source release of
> >> > >
> >> > > Apache
> >> > >
> >> > > NiFi
> >> > >
> >> > > nifi-1.4.0.
> >> > >
> >> > > The source zip, including signatures, digests, etc. can be found
> >> > >
> >> > > at:
> >> > >
> >> > > https://repository.apache.org/content/repositories/
> >> > >
> >> > > orgapachenifi-
> >> > >
> >> > >
> >> > > The Git tag is nifi-1.4.0-RC2
> >> > > The Git commit ID is e6508ba7d3da5bba54abd6233a7a8f9dd4c32151
> >> > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> >> > > e6508ba7d3da5bba54abd6233a7a8f9dd4c32151
> >> > >
> >> > > Checksums of nifi-1.4.0-source-release.zip:
> >> > > MD5: 41e4083e602883a3e180032f32913414
> >> > > SHA1: 26770625138126f45bed4989adb0a6b65a767aa2
> >> > >
> >> > > Release artifacts are signed with the following key:
> >> > > https://people.apache.org/keys/committer/jstorck.asc
> >> > >
> >> > > KEYS file available here:
> >> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >> > >
> >> > > 199 issues were closed/resolved for this release:
> >> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > > projectId=12316020=12340589
> >> > >
> >> > > Release note highlights can be found here:
> >> > > https://cwiki.apache.org/confluence/display/NIFI/
> >> > > Release+Notes#ReleaseNotes-Version-1.4.0
> >> > >
> >> > > The vote will be open for 72 hours.
> >> > > Please download the release candidate and evaluate the necessary
> >> > >
> >> > > items
> >> > >
> >> > > including checking hashes, signatures, build
> >> > > from source, and test.  The please vote:
> >> > >
> >> > > [ ] +1 Release this package as nifi-1.4.0
> >> > > [ ] +0 no opinion
> >> > > [ ] -1 Do not release this package because...
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> > --
> > --
> > *Gerdan Rezende dos Santos *
> > Hortonworks, PostgreSQL & EnterpriseDB Specialist, Support, Training &
> > Services
> > +55 (61) 996 451 525
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi Committer Drew Lim

[Joe Percivall]

Congrats Drew! Very well deserved, always appreciated all your work on
documentation and QA

On Wed, May 31, 2017 at 10:49 PM, Koji Kawamura <ijokaruma...@gmail.com>
wrote:

> Congratulations Drew!!
>
> On Thu, Jun 1, 2017 at 11:47 AM, Yolanda Davis
> <yolanda.m.da...@gmail.com> wrote:
> >
> > Congratulations Drew!
> >
> >
> >> On May 31, 2017, at 4:20 PM, Bryan Rosander <brosan...@apache.org>
> wrote:
> >>
> >> Congrats Drew!
> >>
> >> On Wed, May 31, 2017 at 3:51 PM, Andrew Psaltis <
> psaltis.and...@gmail.com>
> >> wrote:
> >>
> >>> Congrats Drew! I spend a lot of time teaching people about NiFi and can
> >>> honestly say the documentation -- built-in and on the wiki is a great
> >>> selling point. Thanks for all the hard work.
> >>>
> >>>> On Wed, May 31, 2017 at 3:08 PM, Tony Kurc <tk...@apache.org> wrote:
> >>>>
> >>>> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Drew
> >>>> Lim has accepted the PMC's invitation to become a committer on the
> Apache
> >>>> NiFi project. We greatly appreciate all of Drew's hard work and
> generous
> >>>> contributions to the project. We look forward to his continued
> >>> involvement
> >>>> in the project.
> >>>>
> >>>> In my opinion, one of the strengths of NiFi is that someone can launch
> >>> the
> >>>> UI, do some light (often built-in) reading, and get started "making
> data
> >>>> flow" in a short amount of time. Drew has been instrumental in making
> >>> this
> >>>> happen, over the past year contributing to the wiki and making the
> >>> built-in
> >>>> documentation correct and approachable. We all know the Apache adage
> >>>> "Community > Code", and Drew's contributions are key to ensuring the
> >>> health
> >>>> of the community.
> >>>>
> >>>> Welcome and congratulations!
> >>>>
> >>>> --Tony
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Thanks,
> >>> Andrew
> >>>
> >>> Subscribe to my book: Streaming Data <http://manning.com/psaltis>
> >>> <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306>
> >>> twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata>
> >>>
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi Committer Marc Parisi

[Joe Percivall]

Congrats Marc, excited to see what else you can create for MiNiFi!

On Wed, May 31, 2017 at 11:00 PM, Joe Witt <joe.w...@gmail.com> wrote:

> Congrats and welcome.  Kevin said it very well so I'll simply +1 that.
>
> On Wed, May 31, 2017 at 10:45 PM, Kevin Doran <kdoran.apa...@gmail.com>
> wrote:
> >
> >
> >
> >
> >
> >
> > Congratulations, Marc! Very well deserved. Thanks for
> your contributions and generosity with sharing your technical knowledge.
> >
> >
> >
> > _
> > From: Jeremy Dyer <jdy...@gmail.com>
> > Sent: Wednesday, May 31, 2017 10:23 PM
> > Subject: Re: [ANNOUNCE] New Apache NiFi Committer Marc Parisi
> > To:  <dev@nifi.apache.org>
> >
> >
> > Congratulations Marc! Have really enjoyed working and learning from you
> on the C++ side of the house. Look forward to your further work!
> >
> > Sent from my iPhone
> >
> >> On May 31, 2017, at 9:37 PM, Tony Kurc <tk...@apache.org> wrote:
> >>
> >> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Marc
> >> Parisi has accepted the PMC's invitation to become a committer on the
> >> Apache NiFi project. We greatly appreciate all of Marc's hard work and
> >> generous contributions to the project. We look forward to his continued
> >> involvement in the project.
> >>
> >> Marc has been contributing heavily to MiNiFi C++ for the past several
> >> months, really bringing energy to that piece of the project. He's been
> >> making heavy code contributions, and as many of you have discovered,
> active
> >> and helpful on the mailing lists and is a willing reviewer. Marc also
> >> brings with him experience with another Apache project, Accumulo, where
> he
> >> is a committer and PMC member.
> >>
> >> Welcome and congratulations!
> >>
> >> Tony
> >
> >
> >
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi PMC Member - Pierre Villard

[Joe Percivall]

Congrats and welcome Pierre!

On Tue, May 23, 2017 at 11:21 AM, Bryan Rosander <brosan...@apache.org>
wrote:

> Congrats Pierre!
>
> On Tue, May 23, 2017 at 11:19 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
> > Thanks all! Very much appreciated!! Looking forward the amazing stuff to
> > come!
> >
> > 2017-05-23 1:30 GMT+02:00 Andre <andre-li...@fucs.org>:
> >
> > > Pierre,
> > >
> > > Your contribution to NiFi takes many forms but I would like to thank
> you
> > > for the amazing blogs you have put together!
> > >
> > > I am sure many in the user and dev lists will vouch that your blog
> > contains
> > > some of the first posts people will refer to when they start to use
> NiFi
> > > and when they try to step up the ladder on their use of the
> functionality
> > > of the platform.
> > >
> > > Thank you and welcome aboard!!!
> > >
> > >
> > > On Tue, May 23, 2017 at 5:17 AM, Tony Kurc <tk...@apache.org> wrote:
> > >
> > > > On behalf of the Apache NiFi PMC, I am pleased to announce that
> Pierre
> > > > Villard has accepted the PMC's invitation to join the Apache NiFi
> PMC.
> > > We
> > > > greatly appreciate all of Pierre's hard work and generous
> contributions
> > > to
> > > > the project. We look forward to continued involvement in the project.
> > > >
> > > > Pierre has been a long time code contributor to both NiFi and MiNiFi.
> > In
> > > > addition to that, he's spurred the community through his blogging -
> > > > teaching people how to use, operate, and monitor NiFi. He's a
> prolific
> > > > reviewer of contributions, and active in the important task of
> > verifying
> > > > releases.
> > > >
> > > > Please join us in congratulating and welcoming Pierre to the Apache
> > NiFi
> > > > PMC.
> > > >
> > > > Congratulations and welcome, Pierre!
> > > >
> > > > -- Tony
> > > >
> > >
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi PMC Member - Yolanda Davis

[Joe Percivall]

Glad to have you joining the PMC Yolanda, very well deserved!

On Thu, May 18, 2017 at 12:02 AM, Jeff <jtsw...@gmail.com> wrote:

> Congrats Yolanda!
>
> On Wed, May 17, 2017 at 10:43 PM Yolanda Davis <yolanda.m.da...@gmail.com>
> wrote:
>
> > Thank you everyone! It has been my pleasure to continue to contribute to
> > and support this awesome community. Definitely looking forward to all the
> > great things ahead!
> >
> > On Wed, May 17, 2017 at 10:32 PM, Koji Kawamura <ijokaruma...@gmail.com>
> > wrote:
> >
> > > Congratulations Yolanda, well deserved! I have a great respect for
> > > your excellent work.
> > >
> > > On Thu, May 18, 2017 at 11:15 AM, Andy LoPresto <alopre...@apache.org>
> > > wrote:
> > > > Congratulations Yolanda. Well deserved and very excited for your
> > > continued
> > > > excellent contributions to all aspects of the project.
> > > >
> > > > Andy LoPresto
> > > > alopre...@apache.org
> > > > alopresto.apa...@gmail.com
> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > >
> > > > On May 17, 2017, at 7:14 PM, Joe Witt <joe.w...@gmail.com> wrote:
> > > >
> > > > Agree very much with Tony's excellent writeup.
> > > >
> > > > Congrats and thank you Yolanda!
> > > >
> > > > On Wed, May 17, 2017 at 10:11 PM, Tony Kurc <tk...@apache.org>
> wrote:
> > > >
> > > > On behalf of the Apache NiFi PMC, I am pleased to announce that
> Yolanda
> > > > Davis has accepted the PMC's invitation to join the Apache NiFi PMC.
> > We
> > > > greatly appreciate all of Yolanda's hard work and generous
> > contributions
> > > to
> > > > the project. We look forward to continued involvement in the project.
> > > >
> > > > I know many people have interacted with Yolanda maybe at one of her
> > > > conference talks, or had the pleasure of working with her on reviews,
> > or
> > > > used some of the features she's contributed and put a lot of work
> into
> > > > making them well tested and easy to use. If so, I think you'd agree
> it
> > is
> > > > hard to interact with Yolanda and not get excited about not only NiFi
> > but
> > > > the entire Apache way. If not, you're in for a treat when you get the
> > > > chance!
> > > >
> > > > Please join us in congratulating and welcoming Yolanda to the Apache
> > NiFi
> > > > PMC.
> > > >
> > > > Congratulations and welcome, Yolanda!
> > > >
> > > > -- Tony
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > --
> > yolanda.m.da...@gmail.com
> > @YolandaMDavis
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi Committer Bin Qiu

[Joe Percivall]

A long time coming, congrats Bin!

On Wed, Apr 5, 2017 at 8:56 AM, Pierre Villard <pierre.villard...@gmail.com>
wrote:

> Congrats Bin! Very well deserved!
>
> Le 5 avr. 2017 5:31 AM, "Rob Moran" <rmo...@gmail.com> a écrit :
>
> Thank you and congratulations BIn!
>
> Rob
>
> On Tue, Apr 4, 2017 at 10:44 PM, Joe Skora <jsk...@gmail.com> wrote:
>
> > Congratulations and welcome!
> >
> > On Tue, Apr 4, 2017 at 10:07 PM, Andy LoPresto <alopre...@apache.org>
> > wrote:
> >
> > > Great work Bin.
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > On Apr 4, 2017, at 6:03 PM, Matt Burgess <mattyb...@apache.org> wrote:
> > >
> > > Congratulations Bin!!
> > >
> > > On Tue, Apr 4, 2017 at 8:29 PM, Andre <andre-li...@fucs.org> wrote:
> > >
> > > congrats Bin!
> > >
> > > Looking forward for building a NiFi-CPP cluster in the future (Late
> > > April fool... happy to keep it as MiNiFi-CPP :-) )
> > >
> > > Cheers
> > >
> > >
> > >
> > > On Wed, Apr 5, 2017 at 6:17 AM, Tony Kurc <tk...@apache.org> wrote:
> > >
> > > Apache NiFi community,
> > >
> > >
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Bin
> > > Qiu has accepted the PMC's invitation to become a committer on the
> Apache
> > > NiFi project. We greatly appreciate all of Bin’s hard work and generous
> > > contributions and look forward to continued involvement in the project.
> > >
> > > Bin has been one of the driving forces behind MiNiFi - C++,
> contributing
> > a
> > > massive amount in terms of code and helping with release verification
> and
> > > always being responsive to the community.
> > >
> > >
> > > Congrats, Bin!
> > >
> > >
> > > - Tony
> > >
> > >
> > >
> >
>



-- 
*Joe Percivall*
e: joeperciv...@gmail.com

Re: [ANNOUNCE] New Apache NiFi PMC Member - Oleg Zhurakousky

[Joe Percivall]

Congrats Oleg!

On Wed, Apr 5, 2017 at 8:58 AM, Pierre Villard <pierre.villard...@gmail.com>
wrote:

> Congrats Oleg !
>
>
> Le 5 avr. 2017 5:33 AM, "Rob Moran" <rmo...@gmail.com> a écrit :
>
> > Thank you and congratulations Oleg!
> >
> > Rob
> >
> > On Tue, Apr 4, 2017 at 11:09 PM, Adam Lamar <adamond...@gmail.com>
> wrote:
> >
> > > Congrats Oleg, well deserved!
> > >
> >
>



-- 
*Joe Percivall*
e: joeperciv...@gmail.com

Re: [ANNOUNCE] New Apache NiFi Committer Jeff Storck

[Joe Percivall]

 Congrats Jeff!

On Tue, Feb 21, 2017 at 3:33 PM, Yolanda Davis <yolanda.m.da...@gmail.com>
wrote:

> Congratulations Jeff!
>
> On Tue, Feb 21, 2017 at 2:41 PM, Aldrin Piri <ald...@apache.org> wrote:
>
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that Jeff
> > Storck has accepted the PMC's invitation to become a committer on the
> > Apache NiFi project. We greatly appreciate all of Jeff's hard work and
> > generous contributions and look forward to continued involvement in the
> > project.
> >
> > Jeff's contributions include significant efforts toward upgrade and
> > migration processes inclusive of flow layout when upgrading from 0.x to
> 1.x
> > and the ZooKeeper migration toolkit.
> >
> > Congrats, Jeff!
> >
>
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [VOTE] Release Apache NiFi 0.7.2

[Joe Percivall]

+1 binding



On Mon, Feb 20, 2017 at 4:16 PM, Andy LoPresto <alopre...@apache.org> wrote:

> Adding my vote (forgot to put it here because I prepared the release)
>
> +1, binding
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Feb 19, 2017, at 4:55 PM, Koji Kawamura <ijokaruma...@gmail.com> wrote:
>
> +1 (non-binding)
>
> Built from src on OSX Sierra 10.12.3 (16D32), all tests pass
> Verified sigs and hashes.
> Ran sample flow.
>
> On Mon, Feb 20, 2017 at 5:13 AM, Bryan Rosander <brosan...@apache.org>
> wrote:
>
> +1 (non-binding)
>
> Verified signature, hashes
> Contrib-check build against fresh local repo
> Simple flow on 3 node cluster
>
> On Sat, Feb 18, 2017 at 3:45 PM, Joe Witt <joe.w...@gmail.com> wrote:
>
> James
>
> It is simply enough that someone volunteered to RM the release.  If time is
> available to help review/vote then great.  Same with the 1.x release.
>
> Thanks
> Joe
>
> On Feb 18, 2017 2:59 PM, "James Wing" <jvw...@gmail.com> wrote:
>
> The unifying theme of 0.7.2 and 1.1.2 appears to be NIFI-3487 "Refactor
> user formatting".  Is this urgent?
>
> https://issues.apache.org/jira/browse/NIFI-3487
> https://github.com/apache/nifi/commit/bd88e4335ad151592f1310996e9a05
> 13b7f0829a
>
>
> Thanks,
>
> James
>
>
> On Fri, Feb 17, 2017 at 9:55 AM, Joe Witt <joe.w...@gmail.com> wrote:
>
> Mike,
>
> You're absolutely right that there are some good fixes to be included
> in an upcoming release.  There is no reason someone couldn't put
> together an 0.7.3.
>
> This is just something that we're wanting resolved and have the energy
> to push forward and doesn't require additional testing as inclusion of
> other items would.
>
> Please by no means see this as a deterrent to progression on an 0.7.3.
>
> Thanks
> Joe
>
> On Fri, Feb 17, 2017 at 12:38 PM, Michael Moser <moser...@gmail.com>
> wrote:
>
> I'm sad that 0.7.2 does not contain some of the other bug fixes
>
> currently
>
> on the 0.x branch.  It doesn't seem like it would have cost very much
>
> to
>
> just include them.
>
> +0 (non binding)
>
> -- Mike
>
>
> On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto <
>
> alopre...@apache.org>
>
> wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of
>
> Apache
>
> NiFi
>
> nifi-0.7.2.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/
>
> orgapachenifi-1099
>
>
> The Git tag is nifi-0.7.2-RC1
> The Git commit ID is 831ac6939df7d418cadb336eedb4e09fb97541a1
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 831ac6939df7d418cadb336eedb4e09fb97541a1
>
> Checksums of nifi-0.7.2-source-release.zip:
> MD5: efe9ea1cf0698a57a6829fe3829fc136
> SHA1: aee51164af34394c7017dae491b239a88b614865
> SHA256: 8cd02675003fca837ea0092b622560
>
> 0a4700b905e5214a751ae7ff833263
>
> 193b
>
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 2 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12339601=12316020
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version0.7.2
>
> The vote will be open for 96 hours (over holiday weekend).
> Please download the release candidate and evaluate the necessary
>
> items
>
> including checking hashes, signatures, build
> from source, and test.  The please vote:
>
> [ ] +1 Release this package as nifi-0.7.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>
>
>
>
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [VOTE] Release Apache NiFi 1.1.2

[Joe Percivall]

+1 binding

Only issue I came across, I created a ticket[1] for but it is trivial and
shouldn't block the release.

[1] https://issues.apache.org/jira/browse/NIFI-3507

On Mon, Feb 20, 2017 at 4:15 PM, Andy LoPresto <alopre...@apache.org> wrote:

> Adding my vote (forgot to put it here because I prepared the release)
>
> +1, binding
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Feb 20, 2017, at 12:27 PM, Yolanda Davis <yolanda.m.da...@gmail.com>
> wrote:
>
> +1 (non-binding)
>
> Confirmed hashes and signatures, ran full build and executed a simple flow.
> all looked good.
>
> On Thu, Feb 16, 2017 at 10:37 PM, Andy LoPresto <alopre...@apache.org>
> wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.1.2.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1098
>
> The Git tag is nifi-1.1.2-RC1
> The Git commit ID is 51fad01f5daf33716b8b5379c32ee932d91c8c63
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 51fad01f5daf33716b8b5379c32ee932d91c8c63
>
> Checksums of nifi-1.1.2-source-release.zip:
> MD5: 31d20a09955fac32d5b4147c497deede
> SHA1: 9f8f2ce00397d990dfb0890f9b1ede70dca4f25e
> SHA256: 0f57b5ae7f5e1d7f1289d779df39f20d70af0ffd92cb01b265beb90b309b747e
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 2 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12339600=12316020
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.1.2
>
> The vote will be open for 96 hours (over holiday weekend).
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  The please vote:
>
> [ ] +1 Release this package as nifi-1.1.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>
>
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Nifi in a hung state

[Joe Percivall]

Hello,

Couple of questions, what version of NiFi are you using and what is the
maximum amount of data (approximate size) you are putting into the
attributes of a FlowFile? Specifically, the error looks a lot like this
one[1]. It only comes about if you're pulling more than 64kb into the
attributes of a FlowFile. It slowly messes up the FlowFile repo partition
by partition.

As for starting fresh, just stop NiFi and remove the repo directories
(flowfile_repo, content_repo, provenance_repo). This will remove all data
from the flow but keep your configuration.

For your second question, it's hard to suggest optimizations without
knowing more about your flow and set-up.

[1] https://issues.apache.org/jira/browse/NIFI-3389

Joe

On Mon, Feb 13, 2017 at 8:02 AM, sam <sambo...@streamhub.co.uk> wrote:

> I am trying Nifi to evaluate and it got out of space very soon.  I am
> reading
> approx 150 MB of data from S3 (using ListS3 and FetchS3) every 20 mins and
> posting it to http endpoint. Trying to fix this I already got into hung
> state.
>
> 1. I emptied the content repository but that got Nifi in hung state, I
> cannot empty queues and neither it moves ahead. Gives following error:
>
> 0 FlowFiles (0 bytes) were removed from the queue.
> Failed to drop FlowFiles due to java.io.IOException: All Partitions have
> been blacklisted due to failures when attempting to update
>
> How can I get out of it? I basically want nifi to start fresh and forget
> the
> state of previously read data?
>
> 2.What are the possible optimisations I could do?
>
> Thank you!
>
>
>
> --
> View this message in context: http://apache-nifi-developer-
> list.39713.n7.nabble.com/Nifi-in-a-hung-state-tp14713.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

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

[Joe Percivall]

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 <pierre.villard...@gmail.com
> wrote:

> +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 <joe.w...@gmail.com>:
>
> > 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 NiFi Registry works out quite well to explain both
> > what it is an to be consistent with the marks.  See here for an
> > example of this guidance from ASF naming/marks guidance [1].
> >
> > I view this vote as actually being about the community decision to
> > create this subproject with the stated goals and in that perspective I
> > am a strong +1.  I'm open to alternative names though I do think
> > "Apache NiFi Registry" is nice and descriptive.
> >
> > [1] https://www.apache.org/dev/project-names.html
> >
> > Thanks
> > Joe
> >
> > On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bbe...@gmail.com> wrote:
> > > 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 there was a case where it would be referred to as
> > > only "Apache Registry", but if sub-project names are trademarked on
> > > their own then I do agree we would likely have to call it "NiFi
> > > Registry".
> > >
> > >
> > > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <jperciv...@apache.org
> >
> > wrote:
> > >> 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 initial discussion had.
> > >>
> > >>
> > >> Joe
> > >>
> > >> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <moser...@gmail.com>
> > wrote:
> > >>
> > >>> 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 <
> > >>> ozhurakou...@hortonworks.com> wrote:
> > >>>
> > >>> > +1 Here as well. We desperately need it.
> > >>> >
> > >>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jdy...@gmail.com>
> > 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 <
> > mattyb...@apache.org>
> > >>> > wrote:
> > >>> > >
> > >>> > >> +1 binding
> > >>> > >>
> > >>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bbe...@gmail.com
> >
> > >>> 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
> > >>> > >>

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

[Joe Percivall]

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 initial discussion had.


Joe

On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <moser...@gmail.com> wrote:

> 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 <
> ozhurakou...@hortonworks.com> wrote:
>
> > +1 Here as well. We desperately need it.
> >
> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jdy...@gmail.com> 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 <mattyb...@apache.org>
> > wrote:
> > >
> > >> +1 binding
> > >>
> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bbe...@gmail.com>
> 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 decision and
> > >>> establish consensus.
> > >>>
> > >>> The scope of this project is to define APIs for interacting with
> > >>> resources that one or more NiFi instances may be interested in, such
> > >>> as a flow registry for versioned flows, an extension registry for
> > >>> extensions, and possibly other configuration resources in the future.
> > >>> In addition, this project will provide reference implementations of
> > >>> these registries, with the goal of allowing the community to build a
> > >>> diverse set of implementations, such as a Git provider for versioned
> > >>> flows, or a bintray provider for an extension registry.
> > >>>
> > >>> I am a +1 and looking forward to the future work in this area.
> > >>>
> > >>> The vote will be open for 72 hours and be a majority rule vote.
> > >>>
> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> > >>> [ ]   0 Do not care
> > >>> [ ]  -1 Do not establish Registry, a subproject of Apache NiFi
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Bryan
> > >>>
> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
> > >> gmail.com%3E
> > >>
> >
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Daffodil/DFDL NiFi Processors

[Joe Percivall]

est file. However, the PCAP schema,
> > found here
> >
> >   https://github.com/DFDLSchemas/PCAP
> >
> > is a bit more interesting, describing multiple layers of the network
> > stack of a packet capture file, showing things like IPv6, IPv4, MAC/IP
> > addresses, ports, protocols, etc. The PCAP DFDL schema is in the
> > src/main/resources/xsd directory, with some example PCAP files in
> > src/tests/resources/tests. These have all been tested to work with NiFi
> > 1.1.1.
> >
> > Thanks and we look forward to any feedback,
> > - Steve
> >
> >
> > [1]
> > https://opensource.ncsa.illinois.edu/confluence/
> > display/DFDL/Daffodil%3A+Open+Source+DFDL
> > [2] https://www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
> > [3] https://github.com/DFDLSchemas
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: Two more updated video tutorials

[Joe Percivall]

Jenn,

I agree with Joe on the usage of the trademark and the addition of the
video description.

I also just want to express my gratitude for you making these videos. I've
had to onboard/introduce a number of people to NiFi and always reference
your videos. They're great!

Thanks Jenn,
Joe



On Fri, Feb 3, 2017 at 9:30 AM, Joe Witt <joe.w...@gmail.com> wrote:

> Jenn,
>
> It is certainly appropriate to use the logo there.  Probably is good
> to have the description of the video indicate that Apache, NiFi, and
> Apache NiFi are trademarks of the Apache Software Foundation.  As
> found here: https://www.apache.org/foundation/marks/faq/#booktitle
>
> It looks like a good description field would be
>
> Apache®, Apache NiFi, NiFi, and the tear drop logo are either
> registered trademarks or trademarks of the Apache Software Foundation
> in the United States and/or other countries. No endorsement by The
> Apache Software Foundation is implied by the use of these marks.
>
> That said I'm by no means an expert on the exact rules but this seems
> reasonable.
>
> Great videos!
>
> Thanks
> Joe
>
> On Fri, Feb 3, 2017 at 8:22 AM, Jennifer Barnabee
> <jennifer.barna...@gmail.com> wrote:
> > Hello NiFi Dev Team -
> > I've created two more updated NiFi tutorial videos. These are updates to
> > the "How to Build a Flow" videos - parts 1 & 2 -- that I did before, but
> > now with the new user interface. You can find the links below, along with
> > the embed code - in case you want to use them.
> >
> > I have a question about my use of the Apache NiFi logo in the beginning.
> Is
> > that acceptable? Do I need to add any type of copyright or anything with
> > that? I figured I should ask here - in case others might want to know. I
> > read the information about the ASF trademark policies, and I saw the
> > copyright for that logo on the NiFi web site. But I didn't see anything
> > specifically for the Apache NiFi logo. Do I use the same verbiage? I can
> > easily update the videos to either remove the logo or add whatever is
> > appropriate.
> >
> > Thanks.
> > -Jenn
> >
> >
> >
> > *How to Build a Flow Part 1 *- https://youtu.be/bzqP-Loyq-Y
> >
> > Embed code:
> > https://www.youtube.com/embed/bzqP-Loyq-Y; frameborder="0"
> > allowfullscreen>
> >
> >
> >
> > *How to Build a Flow Part 2 *- https://youtu.be/YVMUnfjMGVk
> >
> > Embed code:
> > https://www.youtube.com/embed/YVMUnfjMGVk; frameborder="0"
> > allowfullscreen>
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [DISCUSS] Idea for visual access control policy application

[Joe Percivall]

There are of course UI/UX improvements to be made but as a rough concept, I
really like the idea. It reminds me a lot of the origin story of NiFi;
where instead of having to map out the dataflow in Visio-like program each
time a manager wanted to see the current flow (and it'd be outdated an hour
later), the tool was self-documenting. This way the security policies of
the dataflow would be self-documenting as well.

Security is integral to NiFi itself so giving the option to visualize the
security policies as a first class citizen would be a great new feature.

- Joe

On Wed, Jan 18, 2017 at 6:16 PM, larry mccay <larry.mc...@gmail.com> wrote:

> That seems like a really interesting integrated visualization of security
> concerns!
> You would still need the complexities in the definition of the "security
> zone" I imagine.
>
>
> On Wed, Jan 18, 2017 at 3:38 PM, Andy LoPresto <alopre...@apache.org>
> wrote:
>
>> I just opened NIFI-3370 [1] for “apply access control polices
>> simultaneously to multiple selected components” and related it to a
>> previous large ticket NIFI-3115 [2] “enhance user policy management
>> functionality” with a grab bag of thoughts I had on that. I had another
>> idea for this but it’s a little out of left field so I wanted to get some
>> community feedback before I opened a ticket and see if people thought it
>> was a good idea or too confusing/unnecessary.
>>
>> Imagine the concept of “security zones” on the canvas. I diagrammed these
>> with labels currently, but we could obviously modify the appearance
>> sufficiently (forgive the screenshot; I was in the middle of reviewing a PR
>> that doesn’t include restricted processors, nor was it secured). The zone
>> gets one or more policies defined (in my example “Not accessible by Matt”
>> or “Accessible only by HR group”) and then components can be dragged
>> into/out of the zone by an authorized user. Once a component is in the zone
>> (and snapping would be enabled to remove ambiguity about what is in or out
>> if it overlaps), it inherits the policies defined by that zone. The
>> policies could be marked by origin (inherited from zone, applied manually,
>> etc.) and there is an audit log, so if the component is dragged out of the
>> zone, any policies only inherited from that zone could be removed and it
>> would “re-inherit” just the root policies. For only one or two components,
>> it doesn’t save much time, but you could drag snippets, flow sections, and
>> process groups in and out of the zone.
>>
>> I think this would make visual assignment and recognition of (sometimes
>> complex) policies much easier, and greatly reduce the amount of dialogs and
>> searches that occur.
>>
>> Very interested in feedback from the group at large. Could just be a wild
>> goose chase and there are better solutions out there.
>>
>> [1] https://issues.apache.org/jira/browse/NIFI-3370
>> [2] https://issues.apache.org/jira/browse/NIFI-3115
>>
>>
>> Andy LoPresto
>> alopre...@apache.org
>> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>>
>>
>


-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi Committer Joey Frazee

[Joe Percivall]

Very well deserved. Thank you for you contributions so far Joey and
congrats!

On Tue, Jan 3, 2017 at 2:48 PM, Pierre Villard <pierre.villard...@gmail.com>
wrote:

> Congrats Joey!
>
> 2017-01-03 20:44 GMT+01:00 Suneel Marthi <smar...@apache.org>:
>
> > Congrats @Joey
> >
> > On Tue, Jan 3, 2017 at 2:42 PM, Aldrin Piri <ald...@apache.org> wrote:
> >
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Joey
> > > Frazee has accepted the PMC's invitation to become a committer on the
> > > Apache NiFi project. We greatly appreciate all of Joey's hard work and
> > > generous contributions and look forward to continued involvement in the
> > > project.
> > >
> > > Joey's contributions including support for HL7, JMS, and EventHub
> > > extensions.  Joey can also be found assisting with the lists, as well
> as
> > > articles and repositories based around the NiFi community.
> > >
> > > Congrats, Joey!
> > >
> >
>



-- 
*Joe Percivall*
linkedin.com/in/Percivall
e: jperciv...@apache.com

Re: [ANNOUNCE] New Apache NiFi PMC Member - Joe Skora

[Joe Percivall]

Congrats Joe!

On Thu, Dec 29, 2016 at 1:11 PM, Tony Kurc  wrote:

> Glad to have you on the PMC, Joe!
>
> On Thu, Dec 29, 2016 at 1:02 PM, Aldrin Piri  wrote:
>
> > All,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Joe
> Skora has
> > accepted the PMC's invitation to join the Apache NiFi PMC.  Joe has been
> > with NiFi for quite some time, even before its arrival in the ASF and
> > became a committer in February.  We are most pleased he brought his
> > knowledge and supported the community once open sourced and has has
> > provided continuous and excellent contributions in all facets of the
> > community.  Of note, Joe was our first community member to carry out a
> > release without being a PMC member for 0.7.1.
> >
> > Please join us in congratulating and welcoming Joe to the Apache NiFi
> PMC.
> >
> > Again, congratulations Joe and well deserved!
> >
>



-- 

- - - - - -
*Joseph Percivall*
e: joeperciv...@gmail.com

Re: [DISCUSS] Official Apache NiFi Docker Image

[Joe Percivall]

+1

Great idea Jeremy. I love even more all of the "I volunteer" statements
throughout, haha.

Per Joey's point regarding single vs cluster, I'd say it is probably better
to get an mvp of standalone first. Also I'd think the use-cases that would
be using docker wouldn't need to be clustered. Do you see it differently?

Joe

On Wed, Dec 28, 2016 at 10:01 AM, Joey Frazee 
wrote:

> +1
>
> I think this is a great idea because there are at least half a dozen or
> more Dockerfiles and published images floating around. Having something
> that is endorsed and reviewed by the project should help ensure quality.
>
> One question though: Will the images target a single instance NiFi or a
> cluster, e.g., using compose? Or both?
>
> -joey
>
> > On Dec 28, 2016, at 8:55 AM, Jeremy Dyer  wrote:
> >
> > Team,
> >
> > I wanted to discuss getting an official Apache NiFi Docker image similar
> to
> > other Apache projects like storm [1], httpd [2], thrift [3], etc.
> >
> > Official Docker images are hosted at http://www.dockerhub.com and made
> > available to the Docker runtime of end users without them having to build
> > the images themselves. The process of making a Docker image "official",
> > meaning that it is validated and reviewed by a community of Docker folks
> > for security flaws, best practices, etc, works very closely to how our
> > standard contribution process to NiFi works today. We as a community
> would
> > create our Dockerfile(s) and review them just like we review any JIRA
> today
> > and then commit that against our codebase.
> >
> > There is an additional step from there in that once we have a commit
> > against our codebase we would need an "ambassador" (I happily volunteer
> to
> > handle this if there are no objections) who would open a Github Pull
> > Request against the official docker image repo [4]. Once that PR has
> > successfully been reviewed by the official repo folks it would be hosted
> on
> > Dockerhub and readily available to end users.
> >
> > In my mind the steps required to reach this goal would be.
> > 1. Create NiFi, MiNiFi, MiNiFi-CPP JIRAs for creating the initial folder
> > structure and baseline Dockerfiles in each repo. I also volunteer myself
> to
> > take this on as well.
> > 2. Once JIRA is completed, reviewed, and community thumbs up is given I
> > will request the Dockerhub repo handle of "library/apachenifi" with the
> > maintainer of that repos contact email as 
> > 2a). I suggest we follow the naming structure like
> > "library/apachenifi:nifi-1.1.0", "library/apachenifi:minifi-0.1.0",
> > "libraryapachenifi:minifi-cpp-0.1.0". This makes our official image much
> > more clean than having 3 separate official images for each subproject.
> > 3) I will open a PR against [4] with our community Dockerfiles
> > 4) After each release I will continue to open pull requests against [4]
> to
> > ensure the latest releases are present.
> >
> > Please let me know your thoughts.
> >
> > [1] - https://hub.docker.com/r/library/storm/
> > [2] - https://hub.docker.com/_/httpd/
> > [3] - https://hub.docker.com/_/thrift/
> > [4] - https://github.com/docker-library/official-images
> >
> > Thanks,
> > Jeremy Dyer
>

[ANNOUNCE] Apache NiFi 1.1.1 release

[Joe Percivall]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi
1.1.1.

Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data.  Apache NiFi was made for dataflow.  It supports highly
configurable directed graphs of data routing, transformation, and system
mediation logic.

More details on Apache NiFi can be found here:
https://nifi.apache.org/

The release artifacts can be downloaded from here:
https://nifi.apache.org/download.html

Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338797

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.1.1

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi 1.1.1

[Joe Percivall]

Hello

The release passes with

5 +1 (binding) votes
9 +1 (non-binding) votes0 -1 (binding) votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread: 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201612.mbox/%3C733913565.8825942.1482186949105%40mail.yahoo.com%3E

Re: [ANNOUNCE] New Apache NiFi Committer Jeremy Dyer

[Joe Percivall]

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  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 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 project.

>

> Jeremy’s contributions include creation a suite of the processors that
aided

> in parsing HTML, build improvement and testing for MiNiFi, as well as many

> articles and presentations on using NiFi in new and novel ways.

>

> Welcome Jeremy!

-- 
Sent from Gmail Mobile

Apache NiFi 1.1.1 RC1 Release Helper Guide

[Joe Percivall]

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 maven artifact repository

# Pull down nifi-1.1.1 source release artifacts for review:

  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.1.1/nifi-1.1.1-source-release.zip
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.1.1/nifi-1.1.1-source-release.zip.asc
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.1.1/nifi-1.1.1-source-release.zip.md5
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.1.1/nifi-1.1.1-source-release.zip.sha1
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.1.1/nifi-1.1.1-source-release.zip.sha256

# Verify the signature
  gpg --verify nifi-1.1.1-source-release.zip.asc

# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread
  md5sum nifi-1.1.1-source-release.zip
  sha1sum nifi-1.1.1-source-release.zip
  sha256sum nifi-1.1.1-source-release.zip

# Unzip nifi-1.1.1-source-release.zip

# Verify the build works including release audit tool (RAT) checks
  cd nifi-1.1.1
  mvn clean install -Pcontrib-check

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.

Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi 1.1.1 (RC1)

[Joe Percivall]

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 commit hash is a92f2e36ed6be695e4dc6f624f6b3a96e6d1a57c
* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=a92f2e36ed6be695e4dc6f624f6b3a96e6d1a57c
* https://github.com/apache/nifi/commit/a92f2e36ed6be695e4dc6f624f6b3a96e6d1a57c

Checksums of nifi-1.1.1-source-release.zip:
MD5: 74955060d8ee295d77a23607ac644a6e
SHA1: 82efc0dc3141d0fad0205b33539e5928da87ad17
SHA256: 25fab8d7abfecf4c0ccef1ed9cd5f0849c829c0741142ed4074bc8dd0781f7d0

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jpercivall

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

16 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338797
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.1.1

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. Then
please vote:

[ ] +1 Release this package as nifi-1.1.1
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!

[RESULT][VOTE] Release Apache NiFi 1.0.1

[Joe Percivall]

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: 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201612.mbox/%3c1666073387.6252483.1481901492...@mail.yahoo.com%3E

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

[Joe Percivall]

+1 (binding)


- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Monday, December 19, 2016, 9:54:04 AM EST, Mark Payne <marka...@hotmail.com> 
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 and ran through some simple flows. All looks 
good.


> On Dec 16, 2016, at 10:28 AM, Joe Percivall <joeperciv...@yahoo.com.INVALID> 
> wrote:
> 
> I apologize for the improperly formatted message. Hopefully the below message 
> is better.
> 
> 
> 
> 
> Hello Apache NiFi Community,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.1.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1096
> 
> The Git tag is nifi-1.0.1-RC1
> The Git commit hash is 1890f6c522514027ae46f86601f4771f62cadc6d
> * 
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=1890f6c522514027ae46f86601f4771f62cadc6d
> * 
> https://github.com/apache/nifi/commit/1890f6c522514027ae46f86601f4771f62cadc6d
> 
> Checksums of nifi-1.0.1-source-release.zip:
> MD5: cc7fea9a22c0b48f87dd7152ab83c28c
> SHA1: 88c35d5d3ff9d350473a742cdd8c38204628d343
> SHA256: d9d9628ced5bf3f0f3e0eae7729f4eb507120b072e883e287198fee80fbf9d15
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 6 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338865
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.1
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-1.0.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
> 
> Thanks!
> 
> 
> 
> On Friday, December 16, 2016 10:23 AM, Joe Percivall 
> <joeperciv...@yahoo.com.INVALID> wrote:
> 
> 
> 
> Hello Apache NiFi Community,
> I am pleased to be calling this vote for the source release of Apache 
> NiFi,nifi-1.0.1.
> The source zip, including signatures, digests, etc. can be found 
> at:https://repository.apache.org/content/repositories/orgapachenifi-1096
> The Git tag is nifi-1.0.1-RC1The Git commit hash is 
> 1890f6c522514027ae46f86601f4771f62cadc6d* 
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=1890f6c522514027ae46f86601f4771f62cadc6d*
>  
> https://github.com/apache/nifi/commit/1890f6c522514027ae46f86601f4771f62cadc6d
> Checksums of nifi-1.0.1-source-release.zip:MD5: 
> cc7fea9a22c0b48f87dd7152ab83c28cSHA1: 
> 88c35d5d3ff9d350473a742cdd8c38204628d343SHA256: 
> d9d9628ced5bf3f0f3e0eae7729f4eb507120b072e883e287198fee80fbf9d15
> Release artifacts are signed with the following 
> key:https://people.apache.org/keys/committer/jpercivall
> KEYS file available here:https://dist.apache.org/repos/dist/release/nifi/KEYS
> 6 issues were closed/resolved for this 
> release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338865Release
>  note highlights can be found 
> here:https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.1
> The vote will be open for 72 hours.Please download the release candidate and 
> evaluate the necessary itemsincluding checking hashes, signatures, build from 
> source, and test. Thenplease vote:
> [ ] +1 Release this package as nifi-1.0.1[ ] +0 no opinion[ ] -1 Do not 
> release this package because...
> Thanks!

Re: Apache NiFi 1.0.1 RC1 Release Helper Guide

[Joe Percivall]

Again, I apologize for the mess-up in formatting. Please see below for, 
hopefully, a properly formatted message.


---



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 maven artifact repository

# Pull down nifi-1.0.1 source release artifacts for review:

wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip
wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.asc
wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.md5
wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha1
wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha256

# Verify the signature
gpg --verify nifi-1.0.1-source-release.zip.asc

# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread
md5sum nifi-1.0.1-source-release.zip
sha1sum nifi-1.0.1-source-release.zip
sha256sum nifi-1.0.1-source-release.zip

# Unzip nifi-1.0.1-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-1.0.1
mvn clean install -Pcontrib-check

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.

Thank you for your time and effort to validate the release!







On Friday, December 16, 2016 10:23 AM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:

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 maven artifact repository
# Pull down nifi-1.0.1 source release artifacts for review:
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip 
 wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.asc
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.md5
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha1
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha256
# Verify the signature  gpg --verify nifi-1.0.1-source-release.zip.asc
# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread  md5sum nifi-1.0.1-source-release.zip  sha1sum 
nifi-1.0.1-source-release.zip  sha256sum nifi-1.0.1-source-release.zip
# Unzip nifi-1.0.1-source-release.zip
# Verify the build works including release audit tool (RAT) checks  cd 
nifi-1.0.1  mvn clean install -Pcontrib-check
# Verify the contents contain a good README, NOTICE, and LICENSE.
# Verify the git commit ID is correct
# Verify the RC was branched off the correct git commit ID
# Look at the resulting convenience binary as found in nifi-assembly/target
# Make sure the README, NOTICE, and LICENSE are present and correct
# Run the resulting convenience binary and make sure it works as expected
# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.
Thank you for your time and effort to validate the release! 

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

[Joe Percivall]

I apologize for the improperly formatted message. Hopefully the below message 
is better.




Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi,
nifi-1.0.1.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1096

The Git tag is nifi-1.0.1-RC1
The Git commit hash is 1890f6c522514027ae46f86601f4771f62cadc6d
* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=1890f6c522514027ae46f86601f4771f62cadc6d
* https://github.com/apache/nifi/commit/1890f6c522514027ae46f86601f4771f62cadc6d

Checksums of nifi-1.0.1-source-release.zip:
MD5: cc7fea9a22c0b48f87dd7152ab83c28c
SHA1: 88c35d5d3ff9d350473a742cdd8c38204628d343
SHA256: d9d9628ced5bf3f0f3e0eae7729f4eb507120b072e883e287198fee80fbf9d15

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jpercivall

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

6 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338865
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.1

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. Then
please vote:

[ ] +1 Release this package as nifi-1.0.1
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!



On Friday, December 16, 2016 10:23 AM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:



Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache 
NiFi,nifi-1.0.1.
The source zip, including signatures, digests, etc. can be found 
at:https://repository.apache.org/content/repositories/orgapachenifi-1096
The Git tag is nifi-1.0.1-RC1The Git commit hash is 
1890f6c522514027ae46f86601f4771f62cadc6d* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=1890f6c522514027ae46f86601f4771f62cadc6d*
 https://github.com/apache/nifi/commit/1890f6c522514027ae46f86601f4771f62cadc6d
Checksums of nifi-1.0.1-source-release.zip:MD5: 
cc7fea9a22c0b48f87dd7152ab83c28cSHA1: 
88c35d5d3ff9d350473a742cdd8c38204628d343SHA256: 
d9d9628ced5bf3f0f3e0eae7729f4eb507120b072e883e287198fee80fbf9d15
Release artifacts are signed with the following 
key:https://people.apache.org/keys/committer/jpercivall
KEYS file available here:https://dist.apache.org/repos/dist/release/nifi/KEYS
6 issues were closed/resolved for this 
release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338865Release
 note highlights can be found 
here:https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.1
The vote will be open for 72 hours.Please download the release candidate and 
evaluate the necessary itemsincluding checking hashes, signatures, build from 
source, and test. Thenplease vote:
[ ] +1 Release this package as nifi-1.0.1[ ] +0 no opinion[ ] -1 Do not release 
this package because...
Thanks!

Apache NiFi 1.0.1 RC1 Release Helper Guide

[Joe Percivall]

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 maven artifact repository
# Pull down nifi-1.0.1 source release artifacts for review:
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip 
 wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.asc
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.md5
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha1
  wget 
https://dist.apache.org/repos/dist/dev/nifi/1.0.1/nifi-1.0.1-source-release.zip.sha256
# Verify the signature  gpg --verify nifi-1.0.1-source-release.zip.asc
# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread  md5sum nifi-1.0.1-source-release.zip  sha1sum 
nifi-1.0.1-source-release.zip  sha256sum nifi-1.0.1-source-release.zip
# Unzip nifi-1.0.1-source-release.zip
# Verify the build works including release audit tool (RAT) checks  cd 
nifi-1.0.1  mvn clean install -Pcontrib-check
# Verify the contents contain a good README, NOTICE, and LICENSE.
# Verify the git commit ID is correct
# Verify the RC was branched off the correct git commit ID
# Look at the resulting convenience binary as found in nifi-assembly/target
# Make sure the README, NOTICE, and LICENSE are present and correct
# Run the resulting convenience binary and make sure it works as expected
# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.
Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi 1.0.1 (RC1)

[Joe Percivall]

Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache 
NiFi,nifi-1.0.1.
The source zip, including signatures, digests, etc. can be found 
at:https://repository.apache.org/content/repositories/orgapachenifi-1096
The Git tag is nifi-1.0.1-RC1The Git commit hash is 
1890f6c522514027ae46f86601f4771f62cadc6d* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=1890f6c522514027ae46f86601f4771f62cadc6d*
 https://github.com/apache/nifi/commit/1890f6c522514027ae46f86601f4771f62cadc6d
Checksums of nifi-1.0.1-source-release.zip:MD5: 
cc7fea9a22c0b48f87dd7152ab83c28cSHA1: 
88c35d5d3ff9d350473a742cdd8c38204628d343SHA256: 
d9d9628ced5bf3f0f3e0eae7729f4eb507120b072e883e287198fee80fbf9d15
Release artifacts are signed with the following 
key:https://people.apache.org/keys/committer/jpercivall
KEYS file available here:https://dist.apache.org/repos/dist/release/nifi/KEYS
6 issues were closed/resolved for this 
release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338865Release
 note highlights can be found 
here:https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.1
The vote will be open for 72 hours.Please download the release candidate and 
evaluate the necessary itemsincluding checking hashes, signatures, build from 
source, and test. Thenplease vote:
[ ] +1 Release this package as nifi-1.0.1[ ] +0 no opinion[ ] -1 Do not release 
this package because...
Thanks!

Re: [DISCUSS] NiFi 1.1.1 and NiFi 1.0.1 maintenance releases

[Joe Percivall]

Hey Joe,
Yup, I will take on RM duties for 1.0.1

Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Wednesday, December 14, 2016, 3:13:09 PM EST, Joe Witt  
wrote:Team,

There are a few important behavior fixes for template generation and
import with controller services, fine grained authorization logic, and
publishing to kafka.  These fixes are all in the
nifi-1.2.0-SNAPSHOT/master but these also make sense to get backported
to nifi 1.1.1 and nifi 1.0.1 as appropriate.

JIRAs for 1.0.1
  
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.0.1%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

JIRAs for 1.1.1
  
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.1.1%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

I'll do the 1.1.1 release management honors.  JoeP could you as the
1.0.x RM take on the 1.0.x RM duties?

I've just created the support branches for them and pushed to origin
so please apply commits to those branches.  They are:

support/nifi-1.0.x
support/nifi-1.1.x

Thanks!
Joe

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

[Joe Percivall]

+1 (binding) Release this package as nifi-minifi-cpp-0.1.0

Ran through the helper. Built and tested on OSX 10.10.5 and RHEL 7.2. 
Did run into a bit of a hiccup when RHEL 7.2 when using the GetFile processor a 
relative path wasn't working for the input directory and when I didn't specify 
the "FileFilter" it said "[2016-12-01 17:04:43.461] [minifi log] [error] 
Invalid File Filter regex: regex_error." 
Aside from those two, things worked as expected.

Joe
- - - - - - 
Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Thursday, December 1, 2016, 2:51:05 PM EST, Andy LoPresto 
 wrote:+1 (binding)
I downloaded the assets, verified all checksums and GPG signature, and built 
the app. Initially encountered a problem on OS X 10.11.6 because I used 
ossp-uuid library, but with Aldrin’s help was able to remove that and use 
libuuid. Ran a simple GetFile demo and sent data back to a NiFi instance. 

Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP Fingerprint: 
70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Dec 1, 2016, at 8:18 AM, Ben Qiu  wrote:
+1


On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote:


Hello Apache NiFi Community,>







I am pleased to be calling this vote for the source release of Apache

NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>






The source archive, signature, and digests can be located at:>







Source Archive:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz







GPG armored signature:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc







Source MD5:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5







Source SHA1:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1







Source SHA256:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256











The Git tag is minifi-cpp-0.1.0-RC1>



The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186>



*

https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186







*

https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186











Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:>



MD5: a7155f53d86ef93e37bf28d6e4a0299f>



SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd>



SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d47b66>











Release artifacts are signed with the following key:>



https://people.apache.org/keys/committer/aldrin <

https://people.apache.org/keys/committer/aldrin>>






KEYS file available here:>



https://dist.apache.org/repos/dist/release/nifi/KEYS <

https://dist.apache.org/repos/dist/release/nifi/KEYS>>






15 issues were closed/resolved for this release:>





https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
<
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921











Release note highlights can be found here:>





https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
<
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0











The vote will be open for 72 hours.>



Please download the release candidate and evaluate the necessary items>



including checking hashes, signatures, build from source, and test. Then>



please vote:>







[ ] +1 Release this package as nifi-minifi-cpp-0.1.0>



[ ] +0 no opinion>



[ ] -1 Do not release this package because...>

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

[Joe Percivall]

+1 Release this package as minifi-0.1.0
Ran through the helper. Built and tested on OSX 10.10.5, Windows 8.1 and RHEL 
7.2. Everything worked as expected.

Thanks for acting as RM Aldrin,Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Thursday, December 1, 2016, 12:09:38 AM EST, Aldrin Piri  
wrote:Hello
I am pleased to be calling this vote for the source release of Apache NiFi - 
MiNiFi, minifi-0.1.0.

The source zip, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi/0.1.0/
The Git tag is minifi-0.1.0-RC1
The Git commit ID is 6e7f05d4bef3637a829c17435eb9eff83aa6b810* 
https://git-wip-us.apache.org/ 
repos/asf?p=nifi-minifi.git;a=commit;h=6e7f05d4bef3637a829c17435eb9eff83aa6b810*
 
https://github.com/apache/nifi-minifi/commit/6e7f05d4bef3637a829c17435eb9eff83aa6b810
Checksums of nifi-0.0.1-source-release.zip:
MD5: 9d44398bc1eec7d5596ad425bbb9257b
SHA1: d8043759eb53d815badccf9136a239103aa914dfSHA256: 
c740a2765c74b6bda7ab0ef3ee57353e8c26cb5009f8949a3349af7ded0be181

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/aldrin.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

29 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335482

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Version0.1.0

The vote will be open for 72 hours. 

Please download the release candidate and evaluate the necessary items 
including checking hashes, signatures, build from source, and test.
Then please vote:

[ ] +1 Release this package as minifi-0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

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

[Joe Percivall]

+1 (binding) Release this as nifi-1.1.0

- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Monday, November 28, 2016, 10:25:53 AM EST, Bryan Bende  
wrote:+1 (binding) Release this package as nifi-1.1.0

- Verified everything in release helper
- Ran the resulting binary in standalone mode secure and unsecure and
verified a couple of test flows

The original email said the git commit was
f61e42c65e1c2387591ee368c2148cd5bda646bd
but the commit that actually sets the pom versions to 1.1.0 is the next
commit
https://github.com/apache/nifi/commit/5536f690a81418955442d52687695f65f0a44cd0




On Mon, Nov 28, 2016 at 6:44 AM, Scott Aslan  wrote:

> +1 (non-binding)
>
> - Verified signatures, checksums, LICENSE, NOTICE, and README
> - Built using a full clean build with contrib check successfully on OSX,
> with Oracle JDK 1.8.0_77-b03, mvn 3.3.9
> - Run example data flows on OS X with Chrome Version 54.0.2840.98 (64-bit)
> on
> unsecured instance
> - Run example data flows on OS X with Chrome Version 54.0.2840.98 (64-bit)
> on
> secured instance (using an old 1.0 secured config)
>
>
> Successfully tested:
> * Back pressure UI.
> * New restricted-components permission.
> * Status Color in the UI
> * Canvas component fill color
> * User centric policies view
>
> On Mon, Nov 28, 2016 at 9:15 AM, Matt Gilman 
> wrote:
>
> > +1 Release this package as nifi-1.1.0
> >
> > Ran through numerous configurations including standalone and clustered in
> > both secure and unsecured mode and all is working as excepted.
> >
> > Matt
> >
> > On Sat, Nov 26, 2016 at 1:11 AM, Joe Witt  wrote:
> >
> > > Hello Apache NiFi Community,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi,
> > > nifi-1.1.0.
> > >
> > > The source release zip and convenience binaries, including signatures
> > > and digests can be found at:
> > >  https://dist.apache.org/repos/dist/dev/nifi/1.0.0-rc2/
> > >
> > > The Git tag is nifi-1.1.0-RC2
> > > The Git commit hash is f61e42c65e1c2387591ee368c2148cd5bda646bd
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > f61e42c65e1c2387591ee368c2148cd5bda646bd
> > > * https://github.com/apache/nifi/commit/f61e42c65e1c2387591ee368c2148c
> > > d5bda646bd
> > >
> > > Checksums of nifi-1.1.0-source-release.zip:
> > > MD5: 371fb856d9c3947603239ea98f171f6f
> > > SHA1: 532c2e14e915dfa522254745bbc068aa6620babb
> > > SHA256: dd1d0569f209fd7f179b85a50fe4bf81b3d850c79b13d32cad88982a8234
> a719
> > >
> > > Release artifacts are signed with the following key:
> > >  https://people.apache.org/keys/committer/joewitt
> > >
> > > KEYS file available here:
> > >  https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 268 issues were closed/resolved for this release:
> > >  https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020=12337875
> > >
> > >
> > > Release note highlights can be found here:
> > >  https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.1.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.1.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> >
>
>
>
> --
> *Scott Aslan = new WebDeveloper(*
> *{    "location": {        "city": "Saint Cloud",        "state": "FL",
>    "zip": "34771"    },    "contact": {        "mobile":
> "(321)-591-0870",        "email": "scottyas...@gmail.com
> ",        "linkedin":
> "http://www.linkedin.com/in/scottaslan
> ",        "skype": "astechdev"
> }});*
>

Re: nifi configuration file for process group

[Joe Percivall]

Hello Bala,
Are all your processors HTTP processors? Which processors are you trying to use 
to grab data from the IP? You may want to think about whether you could use 
just a couple processors and update them by hand.
If you have to have many processors that hit the same IP, they all can accept 
source connections and they all allow Expression Language, then you can use 
"GetFile" in order to grab a file with the IP you need. Then ExtractText to put 
the IP address in an attribute and lastly use the attribute with the IP in an 
Expression Language expression. You'll be able to modify the input file 
whenever you need to update the IP and your processors will automatically use 
the new IP.
Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com
 

On Thursday, November 17, 2016 8:51 AM, balacode63 
 wrote:
 

 Hi all,

My use case is,

1)Process group A is having 10 processors which uses same ip address
ex(192.168.1.1) for some processing. ex http post
2) if this ip address is changed, i need to update all the processors.
3) is there any way i can handle this in a configuration file in nifi?
    ex: this configuration data will be used across different processors

Please guide me
Thanks,
Bala









--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/nifi-configuration-file-for-process-group-tp13908.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.


   

Re: Getting the number of logs

[Joe Percivall]

I hadn't received Andy's response before I sent mine to the User's list. For 
tracking, here is a link to my response: 
http://mail-archives.apache.org/mod_mbox/nifi-users/201611.mbox/raw/%3c215272108.1093060.1478740617...@mail.yahoo.com%3E/2
Joe - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: 
joeperciv...@yahoo.com
 

On Wednesday, November 9, 2016 7:53 PM, Andy LoPresto 
<alopre...@apache.org> wrote:
 

 Sai,
I’d suggest you look at using a ControllerStatusReportingTask [1], which 
monitors the processor and provides statistics from that component. If you need 
to use this data within NiFi, you can also use 
SiteToSiteProvenanceReportingTask [2], which can export provenance events as 
data that can be consumed by (the same or a different) instance of NiFi. Both 
of these may be overkill for your use case (the provenance reporting task will 
offload all of the provenance events from the application), and if so, you may 
be able to use counters [3] to do this quickly and easily (but be aware that 
the values are just held in memory, so if you’re writing to ES hourly, you 
should be ok, but they won’t persist across restart). Your initial thought to 
use ExecuteScript would also work. 
I believe Joe Percivall had done some work on SEP and window/aggregate 
calculations before. That may also help with what you are doing. 
Joe Percivall·4:51 PM
Here's the link to the processor: 
https://github.com/JPercivall/nifi/blob/newRollingState/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/RollingWindowAggregator.java
Here's the ticket: 
https://issues.apache.org/jira/browse/NIFI-1682?jql=project%20%3D%20NIFI%20AND%20text%20~%20%22rolling%20window%22

Keep in mind that this work is old and will need to be updated. I do have a 
pending PR for UpdateAttribute with State though: 
https://github.com/apache/nifi/pull/319

[1] 
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html[2]
 
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask/index.html[3]
 
https://community.hortonworks.com/questions/50622/apache-nifi-what-are-counters-in-nifi.html
Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP Fingerprint: 
70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Nov 9, 2016, at 8:14 AM, Peddy, Sai <sai.pe...@capitalone.com> wrote:
Hi All,

I’m currently working on a use case to be able to track the number of 
individual logs that come in and put that information in ElasticSearch. I 
wanted to see if there is an easy way to do this and whether anyone had any 
good ideas?

Current approach I am considering: Route the Log Files coming in – to a Split 
Text & Route Text Processor to make sure no empty logs get through and get the 
individual log count when files contain multiple logs – At the end of this the 
total number of logs are visible in the UI queue, where it displays the 
queueCount, but this information is not readily available to any processor. 
Current thought process is that I can use the ExecuteScript Processor and 
update a local file to keep track and insert the document into elastic search 
hourly.

Any advice would be appreciated

Thanks,
Sai Peddy



The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.




   

Re: [ANNOUNCE] New Apache NiFi PMC Member - Andre Fucs de Miranda

[Joe Percivall]

Congratulations Andre! - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: 
joeperciv...@yahoo.com
 

On Friday, November 4, 2016 4:03 AM, Pierre Villard 
 wrote:
 

 Congrats Andre!

2016-11-04 8:58 GMT+01:00 Andy LoPresto :

> Congratulations Andre. Really excited for your continued contributions and
> valuable security insight.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Nov 3, 2016, at 19:37, Joe Witt  wrote:
> >
> > Team,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Andre
> > Fucs de Miranda has accepted the PMC's invitation to join the Apache
> > NiFi PMC.  Andre's excellent contributions to the project reflect the
> > very best of the power of the Apache Way.  Andre started out in the
> > project as an interested user in October of 2015.  He progressed from
> > asking usage questions to contributing ideas, joined the developer
> > list, started reviewing code and contributing new code, participated
> > in votes and discussions and earned committer status.  Since then he
> > has continued those contributions and gone well beyond by working to
> > reduce our open PR and JIRA count and ensure hygiene in our Git
> > branches.
> >
> > Please join us in congratulating and welcoming Andre to the Apache NiFi
> PMC.
> >
> > Congratulations and welcome, Andre!
>


   

Re: Master build failure with nifi-jolt-transform-json-ui?

[Joe Percivall]

This is likely a side-affect of the DDOS attack on DNS servers on the east 
coast.

http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835

 
Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Friday, October 21, 2016 10:04 AM, Bryan Rosander  
wrote:



Trying to open that in a browser gives the same error and says no healthy
backends, maybe the npm registry is having issues?

Thanks,
Bryan


On Fri, Oct 21, 2016 at 10:02 AM, Joe Gresock  wrote:

> Is anyone else getting a build failure on master?
>
> [WARNING] npm WARN package.json nifi-jolt-transform-json-ui@ No README
> data
> [ERROR] npm http GET
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm http 503
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm http GET
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm http 503
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
> [ERROR] npm ERR! fetch failed
> https://registry.npmjs.org/angular-ui-codemirror/-/
> angular-ui-codemirror-0.3.0.tgz
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project
> nifi-jolt-transform-json-ui: Failed to run task: 'npm --cache-min Infinity
> install' failed. (error code 1) -> [Help 1]
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*
>

Re: IMPORTANT -- Lunch and Learn - NiFi

[Joe Percivall]

Hello Devin,

I'm a bit confused but I don't think you meant to send this to the Apache dev 
mailing list. 

Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Wednesday, October 19, 2016 1:40 PM, Devin Fisher 
 wrote:
New like for Template: (fixed a typo)

https://drive.google.com/open?id=0B_BTD18gUE3CeHAxSExfd3Q2T2s


On Wed, Oct 19, 2016 at 11:23 AM, Devin Fisher <
devin.fis...@perfectsearchcorp.com> wrote:

> This week Info: (Hopefully this one is correct)
>
> 
> Nifi HW Template
>  -- You
> will need this for the Homework.
> Slide Show Presentation
> 
>

Re: [DISCUSS] NiFi 1.1.0 release

[Joe Percivall]

Joe, I think you misread. Edgardo is referring to the Pull Requests that are 
currently open, not the tickets assigned to the 1.1.0 version. 

I think these goals (releasing 1.1.0 and cutting down the PR count) should be 
two different efforts. Doing a thorough job reviewing takes a significant 
amount of time from both the reviewer and contributor. In order to cut it down 
significantly would take much longer than a couple days. 

Also there has already been a lot of great new features and bug fixes 
contributed to the 1.X line and I don't think it's worth holding up a 1.1.0 
release for tickets not assigned to this fix version. As an added bonus though, 
I think many of the tickets tagged as 1.1.0 have PRs already open so closing 
those will make a large dent in the PR count.

 
Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Thursday, October 13, 2016 3:58 PM, Joe Witt  wrote:



There are less than 30 right now.  Many of the roughly 90+ JIRAs
opened on 1.1.0 were easily dispositioned to 1.2.0 or closed or just
had fix versions removed.

We will need to have a push over the next bunch of days to deal with
reviewing/merging/moving the remaining items.

Thanks
Joe


On Thu, Oct 13, 2016 at 3:49 PM, Edgardo Vega  wrote:
> Joe,
>
> There are 75 PRs currently open. Why not make a push over the next bunch of
> days to get them closed and then cut the release after that.
>
> Cheers,
>
> Edgardo
>
> On Thu, Oct 13, 2016 at 12:44 PM, Joe Witt  wrote:
>
>> Team,
>>
>> There have been a ton of bugs fixed a few nice features.  I would like
>> to move to get Apache NiFi 1.1.0 release going pretty much based on
>> where we are now and plan to move most tickets to a new Apache NiFi
>> 1.2.0 version.  We can try to get back on our roughly 6-8 week release
>> schedule and shoot for a mid to late Nov release for NiFi 1.2.0 this
>> way as well. Please advise if anyone has any other views on this. In
>> the mean time I'll get the wheels in motion so you'll be seeing a lot
>> of JIRA/issue updates to move version around.
>>
>> Thanks
>> Joe
>>
>> On Thu, Oct 13, 2016 at 12:02 PM, Tony Kurc  wrote:
>> > Sounds good Joe. I have no issue to you doing the rm'ing for it.
>> >
>> > On Oct 13, 2016 8:19 AM, "Joe Witt"  wrote:
>> >
>> >> Team,
>> >>
>> >> There are a lot of great fixes and improvements on the master line now
>> >> and we're at a good time window to start pushing for a release.  There
>> >> are, however, about 90+ JIRAs assigned to 1.1.0 which are open.  I'm
>> >> going to go through them and remove fix versions where appropriate.
>> >>
>> >> I'm happy to take on RM task for this release though if someone else
>> >> would like to take that on please advise.
>> >>
>> >> Thanks
>> >> Joe
>> >>
>>
>
>
>
> --
> Cheers,
>
> Edgardo

Re: MiNiFi-CPP - Travis targets

[Joe Percivall]

Andre,

This looks like a great list to start with and taking the initiative to get it 
going is better!
 
Thanks Andre! 
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Saturday, October 8, 2016 7:50 AM, Andre F de Miranda  wrote:
devs,

I am working with Aldrin to get CMake going (it is working on Ubuntu 14.04
already  )
and next step is to improve platform coverage by configuring our travis
builds to test the code against particular environments.

I was wondering if you would like to see coverage beyond the following list:

* RHEL 6 (covers RHEL, Centos, Scientific, etc)
* RHEL 7 (same)
* Ubuntu 14.04, 16.04
* Debian (armhf, arm64 via qemu)
* Windows - 64 bit

?

Regards

PS - In case one wonder why skipping Ubuntu 12.04 LTS. The end of support
is 6 months away and I rather invest time sorting the list above first.
Happy to look at adding support to it once the list above is completed.

Re: [ANNOUNCE] New Apache NiFi PMC Member - Matt Burgess

[Joe Percivall]

Congrats Matt! Very well deserved!
 - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com
 

On Friday, October 7, 2016 10:37 AM, Bryan Bende  wrote:
 

 Congrats Matt!

On Fri, Oct 7, 2016 at 10:28 AM, Tony Kurc  wrote:

> On behalf of the Apache NiFI PMC, I am very pleased to announce that Matt
> Burgess has accepted the PMC's invitation to join the Apache NiFi PMC. We
> greatly appreciate all of Matt's hard work and generous contributions to
> the project and all the positive interaction with the community. We look
> forward to his continued involvement in the project.
>
> Welcome and congratulations!
> Tony
>


   

Re: FWD: Contributing to NiFi

[Joe Percivall]

Hello Charles,

Sorry you didn't receive it but actually Matt Burgess sent a response shortly 
after you asked for help[1]. Are subscribed to the dev list?

We always love new contributors and we don't want to have you discouraged from 
contributing due to an email not getting delivered.

[1] 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201608.mbox/%3CCAEV8zdVt_USjSHaNBQ%2BSaHgESES8fDwT6x32XLOWxc24D%3D1Ymw%40mail.gmail.com%3E
 

Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Monday, September 19, 2016 2:21 PM, "char...@thesolusgroupllc.com" 
 wrote:



Since I've heard nothing back from anyone on the NiFi team, I'll consider this 
matter closed.

- Original Message - Subject: Contributing to NiFi
From: char...@thesolusgroupllc.com
Date: 8/24/16 10:10 am
To: dev@nifi.apache.org

Hi,

I'm looking to make some contributions to the Apache NiFi project. The Apache 
Nifi documentation advises the reader to visit the NiFi's JIRA page to find 
tickets that are tagged as "beginner".

I've been to the site, but, I have not discover a way in the UI to filter the 
unresolved issues based on a 'beginner tag'.

I did report a bug 2 days ago (#2625), which I'd like to fix. How do you 
recommend I proceed?

Cheers,
Charles

Re: Saving Templates - Release Fix

[Joe Percivall]

Hello Dave,

Apache NiFi 1.0.0 was actually just announced/released. You can download it 
here: https://nifi.apache.org/download.html

Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Wednesday, August 31, 2016 9:50 AM, Dave Hirko  wrote:
Thank you both – we were using 1.0.0 BETA and the issue arose when using the 
new ListS3 processor, and when there was no SSLContext (which is not always 
needed when accessing objects in S3).  The JIRA issue described what we were 
experiencing exactly.

Glad to hear it will be out soon.



Dave,

The commit that fixes that NPE is in the 1.0.0 release tag.  Are you using
1.0.0-Beta?

On Tue, Aug 30, 2016 at 10:53 AM Bryan Bende  wrote:

> Dave,
>
> Are you using 1.0.0 BETA?
>
> The final 1.0.0 release just passed a vote yesterday and should contain
> this fix.
> It will be announced later today per the 24 hour grace period, along with
> the artifacts being posted to the website.
>
> Thanks,
>
> Bryan
>
>
> On Tue, Aug 30, 2016 at 10:43 AM, Dave Hirko  wrote:
>
> > Already hooked on 1.0 and some of the new processors.
> >
> > The issue relating to saving templates is preventing us from using 1.0
> > unfortunately, although I see this issue has been fixed -
> > https://issues.apache.org/jira/browse/NIFI-2546
> >
> > Is there a release date for 1.1 that would incorporate this fix?
> >
> >
> > Dave Hirko | d...@b23.io | 571.421.7729
> >
> >
>



Dave Hirko | d...@b23.io | 571.421.7729

[ANNOUNCE] Apache NiFi 1.0.0 release

[Joe Percivall]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi
1.0.0.

Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data.  Apache NiFi was made for dataflow.  It supports highly
configurable directed graphs of data routing, transformation, and system
mediation logic.

More details on Apache NiFi can be found here:
https://nifi.apache.org/

The release artifacts can be downloaded from here:
https://nifi.apache.org/download.html

Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12332640

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0

Thank you
The Apache NiFi team

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

[Joe Percivall]

+1 (binding) Release this package as nifi-minifi-cpp-0.0.1

- Ran through the helper 
- Ran a couple simple flows

Everything worked as expected. 

This is a great step for MiNiFi! Thank you Bin and Aldrin for all your hard 
work.
 
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, August 30, 2016 2:26 PM, Aldrin Piri  wrote:
As an aside and in response to all the great feedback received thus far, I
do want to share some additional information on the perspective of the
rationale behind the initial release.

By no means is this considered feature complete, but provides some
functional bits to establish a basis from which to grow.  When we look at
some of the ideas originally set up in terms of management and integrating
with NiFi at large, an initial offering that can talk with NiFi and
espouses many of the same constructs is a first step to that end.  We can
certainly make additional disclaimers about the current state of the C++
implementation known and document them more fully such that users that are
aware of what the community is providing.  Some of these are present, but
we can do a bit better.

Ultimately, this provides additional avenues for folks to contribute and
get involved especially as we look at protocols, extensions, and
establishing of an ecosystem of components between all that NiFi is and the
two offerings of MiNiFi.

Thanks!



On Mon, Aug 29, 2016 at 11:27 PM, Aldrin Piri  wrote:

> Tony,
>
> In terms of the GMock, this transitive inclusion was detected but based
> off versions, as best as I could surmise is now part of Google Test as per
> their repo here: https://github.com/google/googlemock. This inclusion is
> covered in the LICENSE [1]
>
> We can certainly can and should clean up warnings and I will create a JIRA
> to cut those down.  Some are on us, some are on the libraries that are
> compiled as part of the build such that they can be statically linked.
>
> In terms of the missing flow.yml, that was an oversight in documentation.
> I think we can get a bit cleaner on the error if something should happen,
> but given the design and deploy type approach this brings, the inclusion of
> a default one and/or auto generating one seems a bit out of the spirit of
> its original intent.
>
> [1] https://github.com/apache/nifi-minifi-cpp/blob/master/LICENSE#L308
>
> Thanks!
> --aldrin
>
> On Mon, Aug 29, 2016 at 10:46 PM, Andrew Psaltis  > wrote:
>
>> +1 (non-binding) Release this package as nifi-minifi-cpp-0.0.1
>>
>>
>> - Verified signature, hashes, and LICENSE/NOTICE/README
>> - Built source and ran a simple flow with GetFile -> RPG -> Standalone
>> NiFi
>> - Environment -- MiNiFi Ubuntu 16.04.1 LTS and Standalone NiFi OSX
>>
>> I also noticed all of the warnings and at least raised a thought -- should
>> we be making an effort to clean it up now? Are they acceptable? Or as in
>> day's gone by the warning really is a the compiler doing you a favor and
>> saying -- "hey this is wrong and it may bite you" . No implying this
>> should
>> hold up the release, but more of a observation of potential tech-debt.
>>
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> On Mon, Aug 29, 2016 at 10:19 PM, Tony Kurc  wrote:
>>
>> > I had a lot of warnings when I built also, lots of unsigned / signed
>> > comparisons, for example.
>> >
>> > I'm building on a fairly vanilla Ubuntu 14.04 x64_64 box. I can paste if
>> > people are interested.
>> >
>> > On Aug 29, 2016 10:06 PM, "Andy LoPresto"  wrote:
>> >
>> > > Downloaded, verified the GPG signature and checksums, checked the
>> README,
>> > > LICENSE, and NOTICE files. Verified the git commit ID.
>> > >
>> > > Built with make (had to install boost using Homebrew first). I got a
>> > > couple warnings & errors during the make process (documented below) —
>> not
>> > > sure if they are known issues but they did not stop the build from
>> > > completing.
>> > >
>> > > I followed Koji’s lead and used the sample README flow.yml and sent
>> > output
>> > > to a local NiFi instance using S2S. Everything worked great.
>> > >
>> > > +1 (binding)
>> > >
>> > > Noted issues (let me know if you would like me to report these as
>> Jiras):
>> > >
>> > > During `make`:
>> > >
>> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
>> > > -fvisibility=hidden -fPIC -I.. -c clear.c  -o clear.o
>> > > clang: warning: argument unused during compilation: '-rdynamic'
>> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
>> > > -fvisibility=hidden -fPIC -I.. -c compare.c  -o compare.o
>> > > clang: warning: argument unused during compilation: '-rdynamic'
>> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
>> > > -fvisibility=hidden -fPIC -I.. -c copy.c  -o copy.o
>> > > clang: warning: argument unused during compilation: '-rdynamic'
>> > > gcc -g -Wall -rdynamic 

Re: Request for enhancement

[Joe Percivall]

- Moving users list to BCC

Hello Gunjan,

This seems like a good potential idea. The proper place to submit the 
suggestion is through the Apache NiFi Jira[1]. It can more easily be discussed 
and worked on there.

[1] https://issues.apache.org/jira/browse/NIFI


Suggestions/ideas from users are always welcome!

Joe 
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Tuesday, August 30, 2016 12:06 PM, Gunjan Dave  
wrote:



Seems like below didnot get delivered.


On Mon, Aug 29, 2016, 12:30 PM Gunjan Dave 
wrote:

> Hi Team,
> I would like to propose if the following enhacement if seen feasible can
> be incorporated in the provenance graph.
>
> Current graph only shows the type, rather i would like to suggest if we
> can actually put in the component name along with processor type. That
> would make the graph more unique to each flow and more visually intuitive.
>
> just a suggestion, not mandatory.
>

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

[Joe Percivall]

I agree that the error message definitely needs improvement but I don't think 
it's a blocker level issue for an 0.0.1 release.
 

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, August 30, 2016 11:34 AM, Tony Kurc  wrote:
I'm not sure how minor that missing flow.yml issue is - the error message
when flow.yml isn't there is a bit hard to determine what the error was:

"terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct null not valid"





On Mon, Aug 29, 2016 at 2:37 PM, Bryan Bende  wrote:

> +1 (binding) Release this package as nifi-minifi-cpp-0.0.1
>
> - Verified signature, hashes, and LICENSE/NOTICE/README
> - Built source and ran a simple flow with GetFile -> RPG -> Standalone NiFi
>
> Minor note, in the README it said a flow.yml was included in the conf
> directory, but the conf directory only has minifi.properties.
>
>
> On Sun, Aug 28, 2016 at 4:52 PM, Aldrin Piri  wrote:
>
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > MiNiFi C++, nifi-minifi-cpp-0.0.1.
> >
> > The source archive, signature, and digests can be located at:
> >
> > Source Archive:
> >https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.0.1/nifi-minifi-cpp-0.0.1-source.tar.gz
> > GPG armored signature:
> >https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.0.1/nifi-minifi-cpp-0.0.1-source.tar.gz.asc
> > Source MD5:
> >https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.0.1/nifi-minifi-cpp-0.0.1-source.tar.gz.md5
> > Source SHA1:
> >https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.0.1/nifi-minifi-cpp-0.0.1-source.tar.gz.sha1
> > Source SHA256:
> >https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.0.1/nifi-minifi-cpp-0.0.1-source.tar.gz.sha256
> >
> > The Git tag is minifi-cpp-0.0.1-RC1
> > The Git commit hash is 61f0e450ef6604e7028be38f0335e70713ebdea3
> > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.
> > git;a=commit;h=61f0e450ef6604e7028be38f0335e70713ebdea3
> > * https://github.com/apache/nifi-minifi-cpp/commit/
> > 61f0e450ef6604e7028be38f0335e70713ebdea3
> >
> > Checksums of nifi-minifi-cpp-0.0.1-source.tar.gz:
> > MD5: 24121f1ebe3a678d5e2dc84fb8479ef6
> > SHA1: 32c1fb584c9bb484c456cdc4f5dfdd9e91e13364
> > SHA256: c72046d86a9dc34033fa40ad1b2300f1f7915acd369f763e7fc02095d09bb91e
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/aldrin
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 11 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12337990=12319921
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/MINIFI/
> > Release+Notes#ReleaseNotes-Versioncpp-0.0.1
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-minifi-cpp-0.0.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
>

Re: [RESULT][VOTE] Release Apache NiFi 1.0.0

[Joe Percivall]

I apologize, with all the activity I missed a change of vote from -1 to +0 
(non-binding). The updated count is below:

 
7 +1 (binding) votes
8 +1 (non-binding) votes
1 +0 (non-binding) votes
1 -0.9 (non-binding) votes
0 -1 (binding) votes
0 -1 (non-binding) votes



Thanks again to all those who helped make this release possible. This includes 
the hard working developers and those who helped test it!



On Monday, August 29, 2016 8:22 PM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Hello

The release passes with

7 +1 (binding) votes
8 +1 (non-binding) votes
1 -0.9 (non-binding) votes
0 -1 (binding) votes
1 -1 (non-binding) votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread: 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201608.mbox/%3C1857279986.280309.1472228719293%40mail.yahoo.com%3E

[RESULT][VOTE] Release Apache NiFi 1.0.0

[Joe Percivall]

Hello

The release passes with

7 +1 (binding) votes
8 +1 (non-binding) votes
1 -0.9 (non-binding) votes
0 -1 (binding) votes
1 -1 (non-binding) votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread: 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201608.mbox/%3C1857279986.280309.1472228719293%40mail.yahoo.com%3E

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

[Joe Percivall]

Ah sorry, misread your message. I see you ruled out an EOL issue.

Any idea what would change in regards to the SMTP tests in Windows 8 vs 10 (or 
your system vs mine)?

Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Sunday, August 28, 2016 10:10 PM, Joe Percivall <joeperciv...@yahoo.com> 
wrote:
JoeS,

I tested the build on Windows 8 and everything worked fine for me. Wouldn't an 
EOL issue show up in all Windows builds?

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com





On Sunday, August 28, 2016 10:05 PM, Joe Skora <jsk...@gmail.com> wrote:
-1 (non-binding)

It looks good in general, but Windows 10 unit tests consistently fail in
TestListenSMTP.

It builds fine on OS X and Ubuntu has one error described below.

It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.

1. signature verifies
2. hashes verify
3. build and passes RAT check
a. OS X - builds and runs ok
b. Ubuntu 15.10 - builds with one error but runs ok [1]
c. Windows 10 - *FAILS* unit tests:
- Failing tests are
TestListSMTP.validateSuccessfulInteraction
TestListSMTP.validateSuccessfulInteractionWithTls
TestListSMTP.validateTooLargeMessage
   - I tried Git core.autocrlf set to "input" and "false", in case it
was an EOL issue, but that made no difference.
4. LICENSE, NOTICE, and README.MD look good
5. RC commit ID is good
6. RC is branched off correct commit ID
7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
processors
 (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
  HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
  LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
  UpdateAttribute processors)


[1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
build with "--fail-never" to get a binary.  The failing test is
TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
on the box, but the system shows no other problems.  Tracking through the
call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
UnknownHostException on other systems with stacktraces similar to the one
below, but on this one there is no exception thrown using Java 8 and Java 7
only throws the exception if the "-Djava.net.preferIPv4Stack=true" property
is defined.  Since the Mock framework doesn't actually transfer these files
to the bad IP the test expects the files to route to "failure" because fo
the exception but without the exception they go to "success"and the test
fails.
java.net.UnknownHostException: 300.300.300.300: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at TestBadIpAddress.main(TestBadIpAddress.java:13)


On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <bryanrosan...@gmail.com>
wrote:

> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <trk...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> > successfully.
> >
> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >
> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >
> >
> >
> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <joe.w...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full clean build w/contrib check good.
> > >
> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > sources and convenience binaries.
> > >
> > > Verified the commit the release was based on.
> > >
> > > Ran single and multi-node clusters with favorable results.
> > >
> > > For future release please do move any neces

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

[Joe Percivall]

JoeS,

I tested the build on Windows 8 and everything worked fine for me. Wouldn't an 
EOL issue show up in all Windows builds?

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Sunday, August 28, 2016 10:05 PM, Joe Skora <jsk...@gmail.com> wrote:
-1 (non-binding)

It looks good in general, but Windows 10 unit tests consistently fail in
TestListenSMTP.

It builds fine on OS X and Ubuntu has one error described below.

It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.

1. signature verifies
2. hashes verify
3. build and passes RAT check
a. OS X - builds and runs ok
b. Ubuntu 15.10 - builds with one error but runs ok [1]
c. Windows 10 - *FAILS* unit tests:
- Failing tests are
TestListSMTP.validateSuccessfulInteraction
TestListSMTP.validateSuccessfulInteractionWithTls
TestListSMTP.validateTooLargeMessage
   - I tried Git core.autocrlf set to "input" and "false", in case it
was an EOL issue, but that made no difference.
4. LICENSE, NOTICE, and README.MD look good
5. RC commit ID is good
6. RC is branched off correct commit ID
7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
processors
 (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
  HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
  LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
  UpdateAttribute processors)


[1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
build with "--fail-never" to get a binary.  The failing test is
TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
on the box, but the system shows no other problems.  Tracking through the
call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
UnknownHostException on other systems with stacktraces similar to the one
below, but on this one there is no exception thrown using Java 8 and Java 7
only throws the exception if the "-Djava.net.preferIPv4Stack=true" property
is defined.  Since the Mock framework doesn't actually transfer these files
to the bad IP the test expects the files to route to "failure" because fo
the exception but without the exception they go to "success"and the test
fails.
java.net.UnknownHostException: 300.300.300.300: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at TestBadIpAddress.main(TestBadIpAddress.java:13)


On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <bryanrosan...@gmail.com>
wrote:

> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <trk...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> > successfully.
> >
> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >
> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >
> >
> >
> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <joe.w...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full clean build w/contrib check good.
> > >
> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > sources and convenience binaries.
> > >
> > > Verified the commit the release was based on.
> > >
> > > Ran single and multi-node clusters with favorable results.
> > >
> > > For future release please do move any necessary elements of the UnRar
> > > item to NOTICE where category B items belong.  See here for LEGAL
> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> > >
> > > Great job pulling the release together again JoeP.
> > >
> > > Thanks
> > > Joe
> > &

Re: 0.x and master branches are failing to build

[Joe Percivall]

Hello Andre,

Thank you for bringing this up. For master branch, I merged in PR 933 last 
night and it appears something got messed up with the squashing. I am working 
with Matt Gilman to figure out what happened and how to fix it.

For 0.x, I am not sure. Andy LoPresto would have to chime in when he wakes up 
(he's on the West coast).

Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Thursday, August 25, 2016 10:29 AM, Andre  wrote:



devs,

FYI: those who use travis-ci as an indicator of contrib-check is passing,
should be aware travis is experiencing some infrastructure issues and
builds are being severely delayed.

Also, both master and 0.x are failing.

master is failing travis due to style violations on contrib check (Matt B
is reviewing the PR)

While 0.x seems to be failing due  (0.x only fails on Java 7)

Failed tests:
  TestPostHTTPGroovy.testDefaultShouldPreferTLSv1_2:296 assert
selectedProtocol == TLSv1_2
   ||  |
   TLSv1|  TLSv1.2
false

introduced by
https://github.com/apache/nifi/commit/24c0c111343d40188bf8b2de06ebeb39d1cccd88

Cheers

[DISCUSS] Closing in on the Apache 1.0.0 Release

[Joe Percivall]

Hello Team,

Since releasing the Beta a couple weeks ago, there has been continued great 
effort towards
the 1.0.0 release. Many users checked out the Beta and provided feedback in the 
form of 
emails to the dev list and Jiras. With all of that testing and work, we are 
almost ready 
for the 1.0.0 release.

Compared to the number closed already, we have a very small number of tickets 
remaining. 
I will outline each below:

- "On restart of all nodes in nifi cluster one of the nodes failed to join the 
cluster 
with fingerprint mismatch" NIFI-2605[1] [status] Arpit Gupta reported and Mark 
Payne has 
opened a PR, awaiting review.

- "Allow encrypted passwords in configuration files" NIFI-1831[2] [status] 
Reported by 
Andy LoPresto. Andy posted a PR is actively being reviewed.

- "Enhance Status History Dialog" NIFI-2599[3] [status] Scott Aslan reported 
and opened a 
PR. Matt Gilman is reviewing.

- "ModifyBytes should use long instead of int for offsets." NIFI-2411[4] 
[status] Joe 
Skora reported and opened a PR. Awaiting Review.

- "Need to update Encryption Configuration content in Admin guide for 1.0 
changes" 
NIFI-2451[5] [status] Andrew Lim reported and supplied a PR. Joe Witt reviewed 
and +1 but 
is waiting for NIFI-1831 to ensure completeness.

- "Provenance Repository can close Index Reader too soon" NIFI-2600[6] [status] 
Mark Payne
reported and opened a PR. Matt Burgess is reviewing.

- "FingerprintFactory and default property values" NIFI-2606[7] [status] Matt 
Gilman 
reported and is actively working on it.

- "Thread-safety issue with ConsumeKafka" NIFI-2608[8] [status] Oleg 
Zhurakousky reported
and is actively working on it with Joe Witt.

- "Issue determining appropriate site to site URL" NIFI-2609[9] [status] Matt 
Gilman 
reported and Mark Payne posted a PR. Awaiting review.

- "TestProcessorLifecycle and TestStandardProcessScheduler classes causes 
brittle builds 
and appears to be an integration test" NIFI-2610[10] [status] Joe Witt reported 
and Oleg 
Zhurakousky assigned himself.

- "If no ZooKeeper quorum, NiFi does not respond to some web requests" 
NIFI-2617[11] 
[status] Mark Payne reported and opened a PR. Awaiting Review.

There is only one feature left (NIFI-1831) and it already has a PR with active 
reviewing. 
That said, and with the burn rate we've seen over the last couple weeks, I 
expect to start
a vote tomorrow or Wednesday. 

I will continue to keep you all updated.

[1] https://issues.apache.org/jira/browse/NIFI-2605
[2] https://issues.apache.org/jira/browse/NIFI-1831
[3] https://issues.apache.org/jira/browse/NIFI-2599
[4] https://issues.apache.org/jira/browse/NIFI-2411
[5] https://issues.apache.org/jira/browse/NIFI-2451
[6] https://issues.apache.org/jira/browse/NIFI-2600
[7] https://issues.apache.org/jira/browse/NIFI-2606
[8] https://issues.apache.org/jira/browse/NIFI-2608
[9] https://issues.apache.org/jira/browse/NIFI-2609
[10] https://issues.apache.org/jira/browse/NIFI-2610
[11] https://issues.apache.org/jira/browse/NIFI-2617

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com

[ANNOUNCE] Apache NiFi 1.0.0-Beta release

[Joe Percivall]

Hello
The Apache NiFi team would like to announce the release of Apache NiFi
1.0.0-BETA.
The upcoming 1.0.0 release will mark the culmination of a lot of work over
the last few months with many new framework level features being added.
This Beta release was cut to give our Apache NiFi users a chance to help
test this upcoming major release. We encourage users to download the
binary, give the new UI a try, and report any bugs to the Apache NiFi Jira.
https://issues.apache.org/jira/browse/NIFI/
Disclaimer: This release is meant for testing and may not be stable in
terms of features or functionality.
The release artifacts can be downloaded from here:
https://nifi.apache.org/download.html
Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/
Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338066
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0-Beta
Thank youThe Apache NiFi team

Releasing the Beta

[Joe Percivall]

Hello Team,


With the most recent vote thread, Apache NiFi 1.0.0-Beta was approved to be 
released. This is the first "unstable" release[1] aimed at developers and 
testers Apache NiFi has cut and as such I have omitted or modified a couple 
steps from the usual release guide[2]. For the sake of tracking, I will explain 
each below.

I modified the Download page to include "stable" and "unstable" sections[3]. 
Similarly, In SVN I moved the nifi-1.0.0-BETA to "release" but also kept 
0.7.0[4]. 

I did not update the documentation to 1.0.0 docs. 0.7.0 is the most recent 
stable release and what we expect users to be using so the documentation for 
that should be the one available.

For the announcement email, I will be sending it to d...@apache.org and 
us...@apache.org but not annou...@apache.org. This version is primarily for 
providing the ability to our users to test without building from source and as 
such there is no need to send the email to the entire Apache community.

[1] http://www.apache.org/dev/release.html#release-types
[2] https://nifi.apache.org/release-guide.html
[3] https://nifi.apache.org/download.html
[4] https://dist.apache.org/repos/dist/release/nifi/

Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com

Re: [nifi] Git Push Summary

[Joe Percivall]

Hey Joe,

Thanks for catching this! Somehow I did mess up and tagged the 0.7.0-RC2 commit 
as rel/nifi-1.0.0-BETA.

I tried to fix it by overwriting the tag, deleting the previous tag or pushing 
out an empty one but I don't think I have access to modify am existing rel tag. 
I just pushed out a "rel/nifi-1.0.0-BETA-official" tag which correctly points 
to "NIFI-2498-rc1 prepare release nifi-1.0.0-BETA-RC1" and will be getting in 
contact with infra to get the tag names corrected.

Sorry for the mistake and I will reply when it's fixed,
Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, August 9, 2016 10:19 AM, Joe Skora  wrote:
Based on a clone and the GitHub UI, this tag appears to be based on
0.7.0-RC2?


On Mon, Aug 8, 2016 at 5:33 PM,  wrote:

> Repository: nifi
> Updated Tags:  refs/tags/rel/nifi-1.0.0-BETA [created] 0db515d57
>

[RESULT][VOTE] Release Apache NiFi 1.0.0-Beta

[Joe Percivall]

Hello

The release passes with

6 +1 (binding) votes
3 +1 (non-binding) votes0 -1 (binding) votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread: 
http://mail-archives.apache.org/mod_mbox/nifi-dev/201608.mbox/%3C2111728847.9796310.1470429658584.JavaMail.yahoo%40mail.yahoo.com%3E

Re: [VOTE] Release Apache NiFi 1.0.0-BETA (RC1)

[Joe Percivall]

+1 (binding) - Release this package as nifi-1.0.0-BETA.
 
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Monday, August 8, 2016 10:55 AM, Jeff <jtsw...@gmail.com> wrote:



+1 (non-binding)

Checked LICENSE/NOTICE/README are present in the correct location.

Verified MD5 and SHA1 hashes and signature on the source artifact.

Built source artifact with passing contrib-check

Installed the resulting binaries from the .tar.gz and ran NiFi unsecured.
Created a flow using various components, all working as expected.  Checked
Provenance, Summary, Bulletin Board, etc, all working as expected.

Flow Configuration History is not showing the correct value in the User
column, but this has already been reported and a patch is available:
https://issues.apache.org/jira/browse/NIFI-2505


On Mon, Aug 8, 2016 at 9:09 AM Joe Witt <joe.w...@gmail.com> wrote:

> +1 (binding) - Release this package as nifi-1.0.0-BETA.
>
> Items noted:
> - readme.md needs to be udpated to reflect new minimum version of Java.
> - readme.md has references to old nifi versions and probably would be
> best if we updated that
> Captured both: https://issues.apache.org/jira/browse/NIFI-2510
>
> Thanks
> Joe
>
> On Mon, Aug 8, 2016 at 9:00 AM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
> > +1 Release this package as nifi-1.0.0-BETA
> >
> > On Mon, Aug 8, 2016 at 8:52 AM, Mark Payne <marka...@hotmail.com> wrote:
> >
> >> Downloaded source code, verified signatures & hashes and built with
> >> contrib-check.
> >> Was able to start the application and verify that things are working
> >> properly.
> >>
> >> Thanks for taking on the task of Release Manager, Joe!
> >>
> >> +1 (binding) - Release this package as nifi-1.0.0-BETA
> >>
> >>
> >> > On Aug 5, 2016, at 4:40 PM, Joe Percivall <joeperciv...@yahoo.com
> .INVALID>
> >> wrote:
> >> >
> >> > Hello Apache NiFi Community,
> >> >
> >> > I am pleased to be calling this vote for the source release of Apache
> >> NiFi,
> >> > nifi-1.0.0-BETA.
> >> >
> >> > The source zip, including signatures, digests, etc. can be found at:
> >> >
> https://repository.apache.org/content/repositories/orgapachenifi-1089/
> >> >
> >> > The Git tag is nifi-1.0.0-BETA-RC1
> >> > The Git commit hash is 8abcf2ef71334ce8861a81d50f1705b26852a06f
> >> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> >> 8abcf2ef71334ce8861a81d50f1705b26852a06f
> >> > *
> https://github.com/apache/nifi/commit/8abcf2ef71334ce8861a81d50f1705
> >> b26852a06f
> >> >
> >> > Checksums of nifi-1.0.0-BETA-source-release.zip:
> >> > MD5: 830a570cebf04aca8a95f3cd5d58594d
> >> > SHA1: abdcf4655d5e237b94cab579de90db569b938bee
> >> > SHA256:
> 2d3fdff4b284de3a9f9db654ad0c7a0c34760126fae919ca55ba58f309a4338a
> >> >
> >> > Release artifacts are signed with the following key:
> >> > https://people.apache.org/keys/committer/jpercivall
> >> >
> >> > KEYS file available here:
> >> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >> >
> >> > 446 issues were closed/resolved for this release:
> >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12316020=12338066Release note highlights can be found
> >> here:
> >> > https://cwiki.apache.org/confluence/display/NIFI/
> >> Release+Notes#ReleaseNotes-Version1.0.0-Beta
> >> > The vote will be open for 72 hours.
> >> > Please download the release candidate and evaluate the necessary items
> >> > including checking hashes, signatures, build from source, and test.
> Then
> >> > please vote:
> >> >
> >> > [ ] +1 Release this package as nifi-1.0.0-BETA
> >> > [ ] +0 no opinion
> >> > [ ] -1 Do not release this package because...
> >> >
> >> > Thanks!
> >>
> >>
>

Re: [ANNOUNCE] New Apache NiFi Committer Andre Fucs de Miranda

[Joe Percivall]

Congrats Andre!

 
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Sunday, August 7, 2016 3:25 PM, Joe Skora  wrote:



Welcome to the team!


On Saturday, August 6, 2016, Tony Kurc  wrote:

> On behalf of the Apache NiFI PMC, I am very pleased to announce that Andre
> Fucs de Miranda has accepted the PMC's invitation to become a committer on
> the Apache NiFi project. We greatly appreciate all of Andre's hard work and
> generous contributions and look forward to continued involvement in the
> project.
>
> Many of you have already had the pleasure of interacting with him on the
> mailing lists, pull requests or jiras, and have benefited from his
> knowledge and contributions on log processing such as the Lumberjack
> bundle.
>
> Welcome Andre!
>
> Tony
>

Re: [E] Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

[Joe Percivall]

Hello,

Thanks for taking the time to help validate the release but I am not able to 
reproduce those errors (these tests run fine for me). Can you provide some more 
information about your system or how you're running the tests?
 
Thanks,
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Friday, August 5, 2016 5:24 PM, "Tarou, Kirk" 
<kirk.ta...@verizonwireless.com> wrote:
During build, tests failed on nifi-hdfs-processors.

GetHDFSTest.testAutomaticDecompression:153 expected:<1> but was:<0>
  GetHDFSTest.testFileExtensionNotACompressionCodec:191 expected:<1> but
was:<0>
  GetHDFSTest.testGetFilesWithFilter:136 expected:<4> but was:<0>
  GetHDFSTest.testInferCompressionCodecDisabled:172 expected:<1> but
was:<0>







On 8/5/16, 1:41 PM, "Joe Percivall" <joeperciv...@yahoo.com.INVALID> wrote:

>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 maven artifact repository
>
># Pull down nifi-1.0.0-BETA source release artifacts for review:
>
>wget 
>https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BET
>A-source-release.zip
>wget 
>https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BET
>A-source-release.zip.asc
>wget 
>https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BET
>A-source-release.zip.md5
>wget 
>https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BET
>A-source-release.zip.sha1
>wget 
>https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BET
>A-source-release.zip.sha256
>
># Verify the signature
>gpg --verify nifi-1.0.0-BETA-source-release.zip.asc
>
># Verify the hashes (md5, sha1, sha256) match the source and what was
>provided in the vote email thread
>md5sum nifi-1.0.0-BETA-source-release.zip
>sha1sum nifi-1.0.0-BETA-source-release.zip
>sha256sum nifi-1.0.0-BETA-source-release.zip
>
># Unzip nifi-1.0.0-BETA-source-release.zip
>
># Verify the build works including release audit tool (RAT) checks
>cd nifi-1.0.0-BETA
>mvn clean install -Pcontrib-check
>
># Verify the contents contain a good README, NOTICE, and LICENSE.
>
># Verify the git commit ID is correct
>
># Verify the RC was branched off the correct git commit ID
>
># Look at the resulting convenience binary as found in
>nifi-assembly/target
>
># Make sure the README, NOTICE, and LICENSE are present and correct
>
># Run the resulting convenience binary and make sure it works as expected
>
># Send a response to the vote thread indicating a +1, 0, -1 based on your
>findings.
>
>Thank you for your time and effort to validate the release!

Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

[Joe Percivall]

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 maven artifact repository

# Pull down nifi-1.0.0-BETA source release artifacts for review:

wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BETA-source-release.zip
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BETA-source-release.zip.asc
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BETA-source-release.zip.md5
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BETA-source-release.zip.sha1
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.0.0-BETA/nifi-1.0.0-BETA-source-release.zip.sha256

# Verify the signature
gpg --verify nifi-1.0.0-BETA-source-release.zip.asc

# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread
md5sum nifi-1.0.0-BETA-source-release.zip
sha1sum nifi-1.0.0-BETA-source-release.zip
sha256sum nifi-1.0.0-BETA-source-release.zip

# Unzip nifi-1.0.0-BETA-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-1.0.0-BETA
mvn clean install -Pcontrib-check

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.

Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi 1.0.0-BETA (RC1)

[Joe Percivall]

Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi,
nifi-1.0.0-BETA.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1089/

The Git tag is nifi-1.0.0-BETA-RC1
The Git commit hash is 8abcf2ef71334ce8861a81d50f1705b26852a06f
* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=8abcf2ef71334ce8861a81d50f1705b26852a06f
* https://github.com/apache/nifi/commit/8abcf2ef71334ce8861a81d50f1705b26852a06f

Checksums of nifi-1.0.0-BETA-source-release.zip:
MD5: 830a570cebf04aca8a95f3cd5d58594d
SHA1: abdcf4655d5e237b94cab579de90db569b938bee
SHA256: 2d3fdff4b284de3a9f9db654ad0c7a0c34760126fae919ca55ba58f309a4338a

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jpercivall

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

446 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338066Release
 note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0-Beta
The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. Then
please vote:

[ ] +1 Release this package as nifi-1.0.0-BETA
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!

Re: [DISCUSS] 1.0 Beta Release

[Joe Percivall]

Team,

Glad to hear everyone is on board with a Beta. Sorry for not putting out an 
update earlier but I've been waiting to initiate the vote in order to get the 
all of the lingering framework level feature/improvement tickets in. The last 
one should be wrapping up shortly so look out for an RC vote later today.

@Joe Skora

Glad to hear your excited about 1.x! For the cut off "NiFi Settings" please 
create a sub-task of NiFi-2010 and it will be addressed. 
 
Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Friday, August 5, 2016 10:29 AM, Joe Skora <jsk...@gmail.com> wrote:



I've been playing with 1.x in the evenings, trying to understand the REST
API and it's documentation for NIFI-2237
<https://issues.apache.org/jira/browse/NIFI-2237>.

I really like what I've seen so far, so I thought I'd toss out some
observations before they slip away forever.

The finer grained security model is great!  Both the initial admin and
legacy users file work well.  The policies took me a bit to get my head
wrapped around, but they make sense and offer a very high degree of
control.  The policies were overwhelming at first, and I found myself
wanting some bulk change tools to apply a multiple policies to a user or
add multiple users to a policy, but predefining policies against a group
and just adding users to the groups makes it very manageable.  It might be
useful to have a sample configuration that models the 0.x roles in policies
and groups as a starting point, I see it's in the transition code for the
legacy users, but that still doesn't create groups for the roles.

The UI looks great.  Personally, I find the anchored palettes on the left
obtrusive compared to a toolbar, especially when the "fit" button positions
processors underneath them.  Granted, they can be minimized, but I don't
think the Navigate functionality is accessible elsewhere like the Operate
palette functionality is.  I'm sure it will grow on me.

I've noticed that "NiFi Settings" appears at the top left on the banner
line, slightly cut-off by the tool bar below it.  The div contains that
text within it, but since the banner message is applied as the background
the original text isn't overwritten and still shows sometimes.  It does
seems to go away in some cases, I've noticed it gone, but I haven't
correlated any specific action with it going away.

Great job!  I've been focused mostly on 0.x, so it has been exciting to see
how far 1.x has come.  :-D


On Wed, Aug 3, 2016 at 5:23 PM, Jennifer Barnabee <
jennifer.barna...@gmail.com> wrote:

> +1
>
> Sent from my iPhone
>
> > On Aug 1, 2016, at 10:14 PM, Joe Percivall <joeperciv...@yahoo.com.INVALID>
> wrote:
> >
> > Hey Team,
> >
> > The big ticket elements of 1.0 look to be in a pretty good state. Lots
> of things left to tighten up, primarily docs and bug fixes, but, it seems
> wise for a major release like this to first kick out a Beta[1]. The
> relevant section of the Apache.org link:
> >
> >Releases that are believed to be usable by testers and developers
> outside the project, but perhaps not yet stable in terms of features or
> functionality, are usually referred to as "beta" or "unstable".
> >
> > This will enable us to will open up to the broader base of users that
> normally don't build from source to help test and give us a couple weeks of
> feedback to work with before we do a formal 1.0 release vote.
> >
> > If no one has any objections, I will start an RC vote for it later this
> week.
> >
> > [1] http://www.apache.org/dev/release.html#release-types
> >
> > Joe
> > - - - - - -
> > Joseph Percivall
> > linkedin.com/in/Percivall
> > e: joeperciv...@yahoo.com
>

[DISCUSS] 1.0 Beta Release

[Joe Percivall]

Hey Team,

The big ticket elements of 1.0 look to be in a pretty good state. Lots of 
things left to tighten up, primarily docs and bug fixes, but, it seems wise for 
a major release like this to first kick out a Beta[1]. The relevant section of 
the Apache.org link:

Releases that are believed to be usable by testers and developers outside 
the project, but perhaps not yet stable in terms of features or 
functionality, are usually referred to as "beta" or "unstable". 

This will enable us to will open up to the broader base of users that normally 
don't build from source to help test and give us a couple weeks of feedback to 
work with before we do a formal 1.0 release vote. 

If no one has any objections, I will start an RC vote for it later this week.

[1] http://www.apache.org/dev/release.html#release-types

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com

[ANNOUNCE] Apache NiFi 0.7.0 release

[Joe Percivall]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi
0.7.0.

Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data.  Apache NiFi was made for dataflow.  It supports highly
configurable directed graphs of data routing, transformation, and system
mediation logic.

More details on Apache NiFi can be found here:
http://nifi.apache.org/

The release artifacts can be downloaded from here:
http://nifi.apache.org/download.html

Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0

Thank you
The Apache NiFi team

Re: [DISCUSS] narrowing in on the Apache NiFi 1.0.0 release

[Joe Percivall]

This is going to be an awesome release and I'm excited to see what others think 
of all the great work that has gone into it. I would be more than happy to act 
as the RM for the 1.0. I can start tomorrow looking through the tickets 
assigned to 1.0 and help move them towards completion.

Joe 
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, July 12, 2016 12:14 PM, Joe Witt  wrote:
Team,

There has been a lot of progress for 1.0 and with 0.7 in the final
phases and the first minifi release in the mirror its time to start
pulling 1.0 together.  There are a fairly large number of outstanding
tickets most of which are there from 'back in the day' marking things
as a '1.0' fix version meaning 'the future' or habits of making
tickets and preassigning fix releases even though they're not being
worked just yet.  So cleaning a lot of JIRA stuff up but it looks like
we can start working the RC process fairly soon.

Important remaining finishing touch work is underway.  Of the
remaining 1.0 tickets an important push is to cleanup deprecated
things and leverage Apache Yetus annotations to very clearly
articulate API intent/stability/openness.  For those building on
Apache NiFi it means they'll have better clarity on what is subject to
change and not and for those building Apache NiFi itself it means we
will have more flexibility to change parts of the system which are not
considered public API.  There are a couple really exciting roadmap
items like extension/template registry that Matt/Puspendu have been
discussing lately which will also be a tremendous help for agility
with extensions too.  Other things like variable registry will be key
for that too.

This 1.0 release for those following along the master branch and
associated JIRAs has some really cool updates in it.  For example,
NiFi will now be able to support multiple editors in parallel without
the dreaded "too late you must refresh".  It supports fine grained
authorization logic rather than coarse grained 'system wide' DFM or
Read-Only which makes multiple teams working on the same system have a
far better operational capability.  The UI has been refreshed/updated
and provides a more responsive and effective basis to evolve from.

I'm happy to take on the RM work for the release but if someone else
wants to take a stab at it please advise.

Thanks!
Joe

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

[Joe Percivall]

Dist is updated, the current signature is SHA512. I verified both are stored on 
dist as they should be: 


Joseph-Percivall:verify jpercivall$ gpg -v --verify 
nifi-0.7.0-source-release.zip.asc 
gpg: armor header: Version: GnuPG v1
gpg: assuming signed data in `nifi-0.7.0-source-release.zip'
gpg: Signature made Mon Jul 11 14:45:25 2016 EDT using RSA key ID 22886FEE
gpg: using PGP trust model
gpg: Good signature from "Joseph Percivall (CODE SIGNING KEY) 
<jperciv...@apache.org>"
gpg: binary signature, digest algorithm SHA512


Joseph-Percivall:verify jpercivall$ gpg -v --verify 
nifi-0.7.0-source-release.zip-SHA1.asc nifi-0.7.0-source-release.zip
gpg: armor header: Version: GnuPG v1
gpg: Signature made Sat Jul  9 13:34:06 2016 EDT using RSA key ID 22886FEE
gpg: using PGP trust model
gpg: Good signature from "Joseph Percivall (CODE SIGNING KEY) 
<jperciv...@apache.org>"
gpg: binary signature, digest algorithm SHA1


Sorry for the mix-up,
Joe
 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Monday, July 11, 2016 4:00 PM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Sounds good, in dist I am going to move the SHA1 signature to 
"nifi-0.7.0-source-release.zip-SHA1.asc" and replace 
"nifi-0.7.0-source-release.zip.asc" with a SHA512 signature. I am keeping the 
SHA1 for traceability but when adding the download to the website we will use 
the SHA512.


Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com





On Monday, July 11, 2016 2:41 PM, Joe Witt <joe.w...@gmail.com> wrote:
Totally doable for the artifacts you put up in dist Joe.  Basically
just replacing the asc file.  I'd recommend not worrying about it for
the staged maven artifacts.


On Mon, Jul 11, 2016 at 2:34 PM, Tony Kurc <trk...@gmail.com> wrote:
> Would it be appropriate to regenerate the signatures? I think Joe Witt may
> have done something similar recently without cancelling the RC.
>
>
> On Mon, Jul 11, 2016 at 2:05 PM, Joe Percivall <
> joeperciv...@yahoo.com.invalid> wrote:
>
>> @Tony - I apologize, I did not. I must have accidentally overlooked that
>> section of the Release Signing page. I just added the proper configuration
>> to my gpg.conf file.
>>
>> Thank you for pointing it out,
>> Joe
>> - - - - - -
>> Joseph Percivall
>> linkedin.com/in/Percivall
>> e: joeperciv...@yahoo.com
>>
>>
>>
>>
>> On Monday, July 11, 2016 1:37 PM, Tony Kurc <trk...@gmail.com> wrote:
>> @JoePercivall - did you go through the steps to avoid SHA1 for signing [1]?
>>
>> When verifying (with verbose) the nifi-0.7.0-source-release.zip.asc, I got
>> this in the output:
>>
>> gpg: binary signature, digest algorithm SHA1
>>
>> 1. http://www.apache.org/dev/openpgp.html#sha1
>>
>>
>> On Mon, Jul 11, 2016 at 12:50 PM, James Wing <jvw...@gmail.com> wrote:
>>
>> > +1 (non-binding)
>> >
>> > I ran through the release helper and lightly tested the generated binary.
>> >
>> >
>> > On Sat, Jul 9, 2016 at 11:47 AM, Joe Percivall <
>> > joeperciv...@yahoo.com.invalid> wrote:
>> >
>> > > Hello Apache NiFi Community,
>> > >
>> > > I am pleased to be calling this vote for the source release of Apache
>> > NiFi,
>> > > nifi-0.7.0.
>> > >
>> > > The source zip, including signatures, digests, etc. can be found at:
>> > > https://repository.apache.org/content/repositories/orgapachenifi-1088/
>> > > The Git tag is nifi-0.7.0-RC2
>> > > The Git commit hash is f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > > *
>> > >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > > *
>> > >
>> >
>> https://github.com/apache/nifi/commit/f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > >
>> > > Checksums of nifi-0.7.0-source-release.zip:
>> > > MD5: 3a6af39c481fb0ad3eab5a4ea1a954fd
>> > > SHA1: 33e16b0a73242ddda91f89591c82aa5d6e9c8d21
>> > > SHA256:
>> 56ab3132c1fef31dcf50b716b8e08272075f92e476849360280822e0cdc3e993
>> > >
>> > > Release artifacts are signed with the following key:
>> > > https://people.apache.org/keys/committer/jpercivall
>> > > KEYS file available here:
>> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> > >
>> > > 138 issues were closed/resolved for this release:
>> > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078
>> > > Release note highlights can be found here:
>> > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0
>> > >
>> > > The vote will be open for 72 hours.
>> > > Please download the release candidate and evaluate the necessary items
>> > > including checking hashes, signatures, build from source, and test.
>> Then
>> > > please vote:
>> > >
>> > > [ ] +1 Release this package as nifi-0.7.0
>> > > [ ] +0 no opinion
>> > > [ ] -1 Do not release this package because...
>> > >
>> > > Thanks!
>> > >
>> >
>>

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

[Joe Percivall]

Sounds good, in dist I am going to move the SHA1 signature to 
"nifi-0.7.0-source-release.zip-SHA1.asc" and replace 
"nifi-0.7.0-source-release.zip.asc" with a SHA512 signature. I am keeping the 
SHA1 for traceability but when adding the download to the website we will use 
the SHA512.
 

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Monday, July 11, 2016 2:41 PM, Joe Witt <joe.w...@gmail.com> wrote:
Totally doable for the artifacts you put up in dist Joe.  Basically
just replacing the asc file.  I'd recommend not worrying about it for
the staged maven artifacts.


On Mon, Jul 11, 2016 at 2:34 PM, Tony Kurc <trk...@gmail.com> wrote:
> Would it be appropriate to regenerate the signatures? I think Joe Witt may
> have done something similar recently without cancelling the RC.
>
>
> On Mon, Jul 11, 2016 at 2:05 PM, Joe Percivall <
> joeperciv...@yahoo.com.invalid> wrote:
>
>> @Tony - I apologize, I did not. I must have accidentally overlooked that
>> section of the Release Signing page. I just added the proper configuration
>> to my gpg.conf file.
>>
>> Thank you for pointing it out,
>> Joe
>> - - - - - -
>> Joseph Percivall
>> linkedin.com/in/Percivall
>> e: joeperciv...@yahoo.com
>>
>>
>>
>>
>> On Monday, July 11, 2016 1:37 PM, Tony Kurc <trk...@gmail.com> wrote:
>> @JoePercivall - did you go through the steps to avoid SHA1 for signing [1]?
>>
>> When verifying (with verbose) the nifi-0.7.0-source-release.zip.asc, I got
>> this in the output:
>>
>> gpg: binary signature, digest algorithm SHA1
>>
>> 1. http://www.apache.org/dev/openpgp.html#sha1
>>
>>
>> On Mon, Jul 11, 2016 at 12:50 PM, James Wing <jvw...@gmail.com> wrote:
>>
>> > +1 (non-binding)
>> >
>> > I ran through the release helper and lightly tested the generated binary.
>> >
>> >
>> > On Sat, Jul 9, 2016 at 11:47 AM, Joe Percivall <
>> > joeperciv...@yahoo.com.invalid> wrote:
>> >
>> > > Hello Apache NiFi Community,
>> > >
>> > > I am pleased to be calling this vote for the source release of Apache
>> > NiFi,
>> > > nifi-0.7.0.
>> > >
>> > > The source zip, including signatures, digests, etc. can be found at:
>> > > https://repository.apache.org/content/repositories/orgapachenifi-1088/
>> > > The Git tag is nifi-0.7.0-RC2
>> > > The Git commit hash is f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > > *
>> > >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > > *
>> > >
>> >
>> https://github.com/apache/nifi/commit/f5629062c5e2a6c55fb62255aee74c4f25d93e7b
>> > >
>> > > Checksums of nifi-0.7.0-source-release.zip:
>> > > MD5: 3a6af39c481fb0ad3eab5a4ea1a954fd
>> > > SHA1: 33e16b0a73242ddda91f89591c82aa5d6e9c8d21
>> > > SHA256:
>> 56ab3132c1fef31dcf50b716b8e08272075f92e476849360280822e0cdc3e993
>> > >
>> > > Release artifacts are signed with the following key:
>> > > https://people.apache.org/keys/committer/jpercivall
>> > > KEYS file available here:
>> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> > >
>> > > 138 issues were closed/resolved for this release:
>> > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078
>> > > Release note highlights can be found here:
>> > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0
>> > >
>> > > The vote will be open for 72 hours.
>> > > Please download the release candidate and evaluate the necessary items
>> > > including checking hashes, signatures, build from source, and test.
>> Then
>> > > please vote:
>> > >
>> > > [ ] +1 Release this package as nifi-0.7.0
>> > > [ ] +0 no opinion
>> > > [ ] -1 Do not release this package because...
>> > >
>> > > Thanks!
>> > >
>> >
>>

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

[Joe Percivall]

@Tony - I apologize, I did not. I must have accidentally overlooked that 
section of the Release Signing page. I just added the proper configuration to 
my gpg.conf file.

Thank you for pointing it out,
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Monday, July 11, 2016 1:37 PM, Tony Kurc <trk...@gmail.com> wrote:
@JoePercivall - did you go through the steps to avoid SHA1 for signing [1]?

When verifying (with verbose) the nifi-0.7.0-source-release.zip.asc, I got
this in the output:

gpg: binary signature, digest algorithm SHA1

1. http://www.apache.org/dev/openpgp.html#sha1


On Mon, Jul 11, 2016 at 12:50 PM, James Wing <jvw...@gmail.com> wrote:

> +1 (non-binding)
>
> I ran through the release helper and lightly tested the generated binary.
>
>
> On Sat, Jul 9, 2016 at 11:47 AM, Joe Percivall <
> joeperciv...@yahoo.com.invalid> wrote:
>
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi,
> > nifi-0.7.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1088/
> > The Git tag is nifi-0.7.0-RC2
> > The Git commit hash is f5629062c5e2a6c55fb62255aee74c4f25d93e7b
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=f5629062c5e2a6c55fb62255aee74c4f25d93e7b
> > *
> >
> https://github.com/apache/nifi/commit/f5629062c5e2a6c55fb62255aee74c4f25d93e7b
> >
> > Checksums of nifi-0.7.0-source-release.zip:
> > MD5: 3a6af39c481fb0ad3eab5a4ea1a954fd
> > SHA1: 33e16b0a73242ddda91f89591c82aa5d6e9c8d21
> > SHA256: 56ab3132c1fef31dcf50b716b8e08272075f92e476849360280822e0cdc3e993
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/jpercivall
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 138 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-0.7.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
>

Apache NiFi 0.7.0 RC2 Release Helper Guide

[Joe Percivall]

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 maven artifact repository

# Pull down nifi-0.7.0 source release artifacts for review:

wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.asc
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.md5
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.sha1
wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.sha256

# Verify the signature
gpg --verify nifi-0.7.0-source-release.zip.asc

# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread
md5sum nifi-0.7.0-source-release.zip
sha1sum nifi-0.7.0-source-release.zip
sha256sum nifi-0.7.0-source-release.zip

# Unzip nifi-0.7.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-0.7.0
mvn clean install -Pcontrib-check

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.

Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi 0.7.0 (RC2)

[Joe Percivall]

Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi,
nifi-0.7.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1088/
The Git tag is nifi-0.7.0-RC2
The Git commit hash is f5629062c5e2a6c55fb62255aee74c4f25d93e7b
* 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=f5629062c5e2a6c55fb62255aee74c4f25d93e7b
* https://github.com/apache/nifi/commit/f5629062c5e2a6c55fb62255aee74c4f25d93e7b

Checksums of nifi-0.7.0-source-release.zip:
MD5: 3a6af39c481fb0ad3eab5a4ea1a954fd
SHA1: 33e16b0a73242ddda91f89591c82aa5d6e9c8d21
SHA256: 56ab3132c1fef31dcf50b716b8e08272075f92e476849360280822e0cdc3e993

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jpercivall
KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

138 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. Then
please vote:

[ ] +1 Release this package as nifi-0.7.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!

Re: [VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1)

[Joe Percivall]

+1 (binding)

Ran through the helper and verified functionality. 

 - - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Thursday, July 7, 2016 2:13 PM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Vote forth-coming but regarding Andy's notes/questions:
I agree with using HTTPS links when possible in both files and the couple 
README.md changes.

I don't think there are any plans currently for separate mailing lists/IRC 
nodes. I am in favor of keeping NiFi and MiNiFi together for now to build 
visibility, especially since MiNiFi is a sub-project of NiFi. Once there is a 
steady stream of questions we can revisit it.
If this vote passes, it would be the first release. In order to avoid the 
issues with the sensitive property you suggest would it need to be done for 
this release? 
Technically Connections are referring to the IDs of both the Processor and 
Port. The difference is that the Processor's IDs are set as the same as the 
configured name and for the Ports, the IDs and names are those that are set in 
the target NiFi instance (you're point to a component in another system). As 
you bring up this adds the the limitation that all names must be unique (which 
in small deployments that MiNiFi targets shouldn't be a problem) but makes it 
more user friendly. Enforcing uniqueness was added as part of a contribution 
from Bryan Rosander as a validation check when transforming the config.yml and 
applies to processors, connections, and remote processing groups. 
Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com



On Thursday, July 7, 2016 12:05 AM, Andy LoPresto <alopre...@apache.org> 
wrote:


Hi,
I verified the GPG signature and all hash signatures. Contrib check ran fine. 
I used one of the example config.yml files in the System Admin Guide and 
deployed it to the compiled binary. The tool ran successfully and wrote to a 
log file on my system. I have a couple notes about the release but nothing 
blocking. 
+1 (non-binding)
Notes/questions:
README.md:* Could we use HTTPS links when possible?* The note about the time to 
run a parallel Maven build says on a moderate dev laptop it should complete in 
less than 10 minutes. While true, a more accurate statement would be < 2 
minutes. * The mkdir example references “example-nifi-deploy” and 
“example-minifi-deploy” interchangeably.  * Are there separate MiNiFi mailing 
lists and IRC nodes coming?
System Admin Guide:* Could we use HTTPS links when possible?
config.yml:* Could we please change the default algorithm for protecting 
sensitive property values to something stronger than the current selection? I 
would open a Jira if necessary, but this is one of those things that is really 
better to do before the first release so users have a backward-compatible 
config.yml file moving forward. If we change it in a subsequent release, we 
will need to do significant migration hand-holding. My suggestion would be 
"PBEWITHSHA256AND256BITAES-CBC-BC” which is significantly stronger, but after 
trying a few BC options, I continue to get EncryptionExceptions even though I 
have the JCE unlimited cryptographic strength jurisdiction policy files 
installed, so this may be a 0.0.2 fix. Is BouncyCastle not enabled by default?* 
Question about how processors and connectors reference each other — it appears 
connectors reference source processors by name but destination processors or 
ports by ID? Is this consistent or just demonstrating the flexibility of the 
system? Also, what enforces processor name uniqueness, as this is not an 
existing feature of NiFi.  
All in all looks like a lot of great work and will expand the user base and 
opportunities for NiFi significantly. Thanks. 
Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP Fingerprint: 
70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 6, 2016, at 7:27 PM, Aldrin Piri <aldrinp...@gmail.com> wrote:
Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi
- MiNiFi,
minifi-0.0.1.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1087

The Git tag is minifi-0.0.1-RC1

The Git commit hash is d6ebeda6bce8259f0531e845596562515bdb
*
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=d6ebeda6bce8259f0531e845596562515bdb

*
https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f0531e845596562515bdb

Checksums of minifi-0.0.1-source-release.zip:
MD5: b63355fb419ca09b26fe12485b3bf4a5
SHA1: 4c9352b7d4d53d139a707dbdcd03df73dbfb847d
SHA256: d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/aldrin

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

30 issues were closed/resolved for this release:

Re: Update on 0.7.0 RC2

[Joe Percivall]

Hello Team,

As the theme with 0.7.0 has been, it's one step forward and one step back. 
There has been some great work and most of the issues previously seen were 
addressed but another blocker has been found.

- "Enabled ControllerServices disabled on restart" NIFI-2160[1] [status] PR 
have been posted by Oleg Zhurakousky and Brandon DeVries gave a +1 on the 
ticket but ambiguous about what is the next step. I commented asking for a 
follow-up.

- "PutKafka results in OOME if sending very large delimited file" NIFI-2192[2] 
[status] New issue discovered by Mark Payne that causes OOME. Oleg Zhurakousky 
is working to address it.

[1] https://issues.apache.org/jira/browse/NIFI-2160
[2] https://issues.apache.org/jira/browse/NIFI-2192
 
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Saturday, July 2, 2016 1:02 PM, Joe Percivall <joeperciv...@yahoo.com> wrote:
Hello Team,

There have been two new critical bugs identified by Brandon DeVries and added 
to the 0.7.0 release. The status of the remaining 0.7.0 issues are below.

- "Enabled ControllerServices disabled on restart" NIFI-2160[1] [status] A 
regression due to NIFI-2032 that breaks backwards compatibility. Discussion has 
started between Oleg Zhurakousky and Brandon DeVries.

- "Fingerprint not detecting flow.xml differences" NIFI-2159[2] [status] 
Reported by Brandon. No one has started work on it. NEEDS AN ASSIGNEE

- "Secure clustering returning bad request response" NIFI-2119[3] [status] No 
updates, Andy LoPresto is looking into it.

Again for clarity, NIFI-1974 and NIFI-2089 are listed as 0.7.0 and unresolved 
but have already been merged into 0.7.0. Also due to the reasons highlighted in 
my previous message I will not be tracking NIFI-2120 and it is punted.

[1] https://issues.apache.org/jira/browse/NIFI-2160
[2] https://issues.apache.org/jira/browse/NIFI-2159
[3] https://issues.apache.org/jira/browse/NIFI-2119

Hope everyone has a fun and safe fourth,
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com





On Wednesday, June 29, 2016 9:12 AM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Hello Team,

As most know, the closing of RC1 was due to three issues discovered by Joe 
Witt. A status update for each is below. 


- "Secure clustering returning bad request response" NIFI-2119[1] [status] A 
probable source of the problem was discovered by Matt Gilman, NIFI-1753 a 
security upgrade. Andy LoPresto is looking into a fix.

- "source release produces an extraneous file" NIFI-2120[2] [status] I looked 
into how it would be done and I couldn't find any options in the maven release 
plugin that support excluding specific files from the release. I will be 
punting this, unless if someone with more experience with the maven release 
plugin can fix it.

- "Correct license/notice issues" NIFI-2118[3] [status] I addressed the issues 
identified by Joe Witt and the fix was merged by Matt Burgess.

Again I apologize for not finding this issues earlier and will keep you all up 
to date on any changes. Also since RC1 a commit addressing NIFI-1920[4] has 
been merged into the 0.x branch. I will be including it in RC2. It is a simple 
fix that addresses an inadvertent rollback in UnpackContent.

[1] https://issues.apache.org/jira/browse/NIFI-2119
[2] https://issues.apache.org/jira/browse/NIFI-2120
[3] https://issues.apache.org/jira/browse/NIFI-2118
[4] https://issues.apache.org/jira/browse/NIFI-920

Thank you,
Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com

Re: [VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1)

[Joe Percivall]

Vote forth-coming but regarding Andy's notes/questions:
I agree with using HTTPS links when possible in both files and the couple 
README.md changes.

I don't think there are any plans currently for separate mailing lists/IRC 
nodes. I am in favor of keeping NiFi and MiNiFi together for now to build 
visibility, especially since MiNiFi is a sub-project of NiFi. Once there is a 
steady stream of questions we can revisit it.
If this vote passes, it would be the first release. In order to avoid the 
issues with the sensitive property you suggest would it need to be done for 
this release? 
Technically Connections are referring to the IDs of both the Processor and 
Port. The difference is that the Processor's IDs are set as the same as the 
configured name and for the Ports, the IDs and names are those that are set in 
the target NiFi instance (you're point to a component in another system). As 
you bring up this adds the the limitation that all names must be unique (which 
in small deployments that MiNiFi targets shouldn't be a problem) but makes it 
more user friendly. Enforcing uniqueness was added as part of a contribution 
from Bryan Rosander as a validation check when transforming the config.yml and 
applies to processors, connections, and remote processing groups. 
Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com
 

On Thursday, July 7, 2016 12:05 AM, Andy LoPresto  
wrote:
 

 Hi,
I verified the GPG signature and all hash signatures. Contrib check ran fine. 
I used one of the example config.yml files in the System Admin Guide and 
deployed it to the compiled binary. The tool ran successfully and wrote to a 
log file on my system. I have a couple notes about the release but nothing 
blocking. 
+1 (non-binding)
Notes/questions:
README.md:* Could we use HTTPS links when possible?* The note about the time to 
run a parallel Maven build says on a moderate dev laptop it should complete in 
less than 10 minutes. While true, a more accurate statement would be < 2 
minutes. * The mkdir example references “example-nifi-deploy” and 
“example-minifi-deploy” interchangeably.  * Are there separate MiNiFi mailing 
lists and IRC nodes coming?
System Admin Guide:* Could we use HTTPS links when possible?
config.yml:* Could we please change the default algorithm for protecting 
sensitive property values to something stronger than the current selection? I 
would open a Jira if necessary, but this is one of those things that is really 
better to do before the first release so users have a backward-compatible 
config.yml file moving forward. If we change it in a subsequent release, we 
will need to do significant migration hand-holding. My suggestion would be 
"PBEWITHSHA256AND256BITAES-CBC-BC” which is significantly stronger, but after 
trying a few BC options, I continue to get EncryptionExceptions even though I 
have the JCE unlimited cryptographic strength jurisdiction policy files 
installed, so this may be a 0.0.2 fix. Is BouncyCastle not enabled by default?* 
Question about how processors and connectors reference each other — it appears 
connectors reference source processors by name but destination processors or 
ports by ID? Is this consistent or just demonstrating the flexibility of the 
system? Also, what enforces processor name uniqueness, as this is not an 
existing feature of NiFi.  
All in all looks like a lot of great work and will expand the user base and 
opportunities for NiFi significantly. Thanks. 
Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP Fingerprint: 
70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 6, 2016, at 7:27 PM, Aldrin Piri  wrote:
Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi
- MiNiFi,
minifi-0.0.1.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1087

The Git tag is minifi-0.0.1-RC1

The Git commit hash is d6ebeda6bce8259f0531e845596562515bdb
*
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=d6ebeda6bce8259f0531e845596562515bdb

*
https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f0531e845596562515bdb

Checksums of minifi-0.0.1-source-release.zip:
MD5: b63355fb419ca09b26fe12485b3bf4a5
SHA1: 4c9352b7d4d53d139a707dbdcd03df73dbfb847d
SHA256: d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/aldrin

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

30 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335481

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Version0.0.1

The vote will be open for 72 hours.
Please 

Re: [ANNOUNCE] New Apache NiFi PMC Member - Andy LoPresto

[Joe Percivall]

Congratulations Andy! Excited to have you join the PMC.
 

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Thursday, July 7, 2016 12:46 PM, Andy LoPresto  wrote:



Thanks Joe. It is a pleasure to work on the project and an honor to accept the 
invitation. I look forward to continuing to work alongside all the wonderful 
contributors to NiFi (and now MiNiFi). 


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 7, 2016, at 9:44 AM, Joe Witt  wrote:
>
>On behalf of the Apache NiFI PMC, I am very pleased to announce that
>Andy LoPresto has accepted the PMC's invitation to join the Apache
>NiFi PMC. We greatly appreciate all of Andy's hard work and generous
>contributions to the project with a specific focus on security related
>elements. We look forward to his continued involvement in the project.
>
>Welcome and congratulations!
>

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

[Joe Percivall]

All,

Given the issues I am canceling this vote. Once the three issues outlined by 
Joe, tickets copied below, are resolved I will generate a new RC.  Please look 
for an updated vote RC and helper soon.

Thank you for your efforts and I apologize for not finding these issues prior 
to initiating the vote. If you are able, I still encourage checking out the 
commit and attempting to validate the build yourself.

Extraneous file:
  https://issues.apache.org/jira/browse/NIFI-2120

Licensing concerns
  https://issues.apache.org/jira/browse/NIFI-2118

Functional issue
  https://issues.apache.org/jira/browse/NIFI-2119

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Saturday, June 25, 2016 10:11 PM, Andy LoPresto <alopre...@apache.org> wrote:



After some discussion it is likely that the functional issue is a result of a 
specific configuration combined with this PR [1] for NIFI-1981 [2]. I don’t 
have access to Joe’s system to debug that specific issue, but I vote -1 until 
we know what is going on. 

[1] https://github.com/apache/nifi/pull/508
[2] https://issues.apache.org/jira/browse/NIFI-1981




Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jun 25, 2016, at 4:55 PM, Joe Witt <joe.w...@gmail.com> wrote:
>
>-1 (binding)
>
>As James noted the commit id referenced versus what is used by the tag
>is not aligned.
>
>The git commit referenced is the one that the release was based off of
>whereas the tag one is the result after the release as evident by the
>changing version numbers in the poms.
>
>The tag commit id is c9d94853e2c921d7f1d16bfa0c6b29fbfabcd99c
> and the url is
>https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=c9d94853e2c921d7f1d16bfa0c6b29fbfabcd99c
>
>Checked out the build/signature/hashes/etc.. and those things seem great.
>
>Extraneous file:
> https://issues.apache.org/jira/browse/NIFI-2120
>
>Licensing concerns
> https://issues.apache.org/jira/browse/NIFI-2118
>
>Functional issue
> https://issues.apache.org/jira/browse/NIFI-2119
>
>The licensing and functional issue noted below is what resulted in my
>vote.  The extraneous file issue is just something we should sort out
>but not a biggie.
>
>We presently do not have migration guidance for moving from 0.6 to
>0.7.  This may be correct but wanted to verify.
>
>This looks like a lot of 'stuff' but honestly it is quite close to
>being good to go.  Looking forward to the next RC.
>
>Thanks
>Joe
>
>On Sat, Jun 25, 2016 at 3:39 PM, James Wing <jvw...@gmail.com> wrote:
>
>This feels like a newbie question, but the release tag "nifi-0.7.0-RC1"
>>points to commit c9d9485, one commit ahead of the stated release commit
>>56dc8ae.  Is that expected as part of generating the RC?
>>
>>Thanks,
>>
>>James
>>
>>On Fri, Jun 24, 2016 at 12:34 PM, Joe Percivall <
>>joeperciv...@yahoo.com.invalid> wrote:
>>
>>
>>Hello Apache NiFi Community,
>>>
>>>I am pleased to be calling this vote for the source release of Apache NiFi,
>>>nifi-0.7.0.
>>>
>>>The source zip, including signatures, digests, etc. can be found at:
>>>https://repository.apache.org/content/repositories/orgapachenifi-1083/
>>>
>>>The Git tag is nifi-0.7.0-RC1
>>>The Git commit hash is 56dc8aefac822454f2d4133e8cbde903a628ec5b
>>>*
>>>https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=56dc8aefac822454f2d4133e8cbde903a628ec5b
>>>*
>>>https://github.com/apache/nifi/commit/56dc8aefac822454f2d4133e8cbde903a628ec5b
>>>
>>>Checksums of nifi-0.7.0-source-release.zip:
>>>MD5: 8dc31d1f8103f9679cfe4b9533a4049b
>>>SHA1: dc160c9611dc18523c994cd9086fc7088cc520f4
>>>SHA256: 7df056fb6af0eb9bdb94c17bf5bc2db288ed2b0d0a8ad23127dab5cdf74ce767
>>>
>>>Release artifacts are signed with the following key:
>>>http://pgp.mit.edu/pks/lookup?op=get=0x3C6DBAFE22886FEE
>>>
>>>KEYS file available here:
>>>https://dist.apache.org/repos/dist/release/nifi/KEYS
>>>
>>>131 issues were closed/resolved for this release:
>>>
>>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335078
>>>Release note highlights can be found here:
>>>
>>>https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.0
>>>
>>>The vote will be open for 72 hours.
>>>Please download the release candidate and evaluate the necessary items
>>>including checking hashes, signatures, build from source, and test. Then
>>>please vote:
>>>
>>>[ ] +1 Release this package as nifi-0.7.0
>>>[ ] +0 no opinion
>>>[ ] -1 Do not release this package because...
>>>
>>>

Apache NiFi 0.7.0 RC1 Release Helper Guide

[Joe Percivall]

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 maven artifact repository
# Pull down nifi-0.7.0 source release artifacts for review:
  wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip
  wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.asc
  wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.md5
  wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.sha1
  wget 
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.7.0/nifi-0.7.0-source-release.zip.sha256
# Verify the signature  gpg --verify nifi-0.7.0-source-release.zip.asc
# Verify the hashes (md5, sha1, sha256) match the source and what was provided 
in the vote email thread  md5sum nifi-0.7.0-source-release.zip  sha1sum 
nifi-0.7.0-source-release.zip  sha256sum nifi-0.7.0-source-release.zip
# Unzip nifi-0.7.0-source-release.zip
# Verify the build works including release audit tool (RAT) checks  cd 
nifi-0.7.0  mvn clean install -Pcontrib-check
# Verify the contents contain a good README, NOTICE, and LICENSE.
# Verify the git commit ID is correct
# Verify the RC was branched off the correct git commit ID
# Look at the resulting convenience binary as found in nifi-assembly/target
# Make sure the README, NOTICE, and LICENSE are present and correct
# Run the resulting convenience binary and make sure it works as expected
# Send a response to the vote thread indicating a +1, 0, -1 based on your 
findings.
Thank you for your time and effort to validate the release!Joe 

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

[Joe Percivall]

Hello Team,

Thank you all for helping finishing up all the slated 0.7.0 features. 
Unfortunately I tested the 0.x branch on Windows 8 I ran into a couple issues. 
Two of which are bugs in the test framework that I will fix but the third has 
an unknown exact cause and is a blocker. Each of which is listed below. 

A couple times before during the release process we don't find system specific 
issues until the RC vote has already started. In order to try and alleviate 
that, I encourage each of you to pull the latest of the 0.x branch and build on 
various systems. I have personally run on OS X Yosemite (10.10.5) and Windows 
8. If you run into trouble create an issue and let the team know.

- "NIFI-1824 causes failures on Windows" NIFI-2089[1] [status] BLOCKER, Mark 
Payne is looking into the exact cause.

- "TestProcessorLifecyle fails on Windows" NIFI-2092 [status] I am working on a 
PR with the fix.

- "RemoteProcessGroupStatusTest binds to a static Port" NIFI-2097 [status] Not 
a blocker as it doesn't prevent a build on all systems (just those that have 
something running on port 9990) but I am working on a PR with the fix.
 
Once again, NIFI-1974 is listed as "Patch Available" and 0.7.0 in JIRA but a 
fix has already been merged into 0.x and work is being done for master. Also 
sorry for not sending an update yesterday, I was waiting for a good point to 
give an update but things kept being one step away from finished.

[1] https://issues.apache.org/jira/browse/NIFI-2089
[2] https://issues.apache.org/jira/browse/NIFI-2092
[3] https://issues.apache.org/jira/browse/NIFI-2097

Joe
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Monday, June 20, 2016 11:44 AM, Bryan Bende <bbe...@gmail.com> wrote:
I believe NIFI-1895 should be ready to go for 0.7.0 as well...

https://github.com/apache/nifi/pull/542


On Mon, Jun 20, 2016 at 11:39 AM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:

> Team,
>
> We are doing a great job finishing up tickets. Six more were closed over
> the weekend and most of the others made progress as well. We only have
> three more that are tagged as 0.7.0 in Jira. There are a couple others
> which are unversioned that are close but haven't been identified as
> important enough to hold up the release for so I will not reflect them here.
>
> The current status for those left tagged as 0.7.0:
>
> - "Processors could be started before the Controller Services that they
> depend on" NIFI-2032[1] [status] Oleg Zhurakousky's PR was looked at by
> Andy LoPresto but not clear if more action is needed.
>
> - "Create a processor to extract WAV file characteristics" NIFI-615[2]
> [status] Waiting for Joe Skora to rebase and put changes into a PR (which
> he said he would do today) and for final review from Joe Percivall (me)
> once the changes are made.
>
> - "Create PutTCP Processor" NIFI-1834[3] [status] I took Matt Brown's
> original commit and applied my comments in another commit. Bryan Bende
> reviewed and I am addressing now.
>
> Also NIFI-1974 and NIFI-1850 are marked as 0.7.0 and "Patch Available" in
> Jira but they are already merged into 0.x and work is being done to get it
> into master. I will not reflect them here.
>
> [1] https://issues.apache.org/jira/browse/NIFI-2032
> [2] https://issues.apache.org/jira/browse/NIFI-615
>
> [3] https://issues.apache.org/jira/browse/NIFI-1834
>
>
> Joe
> - - - - - -
> Joseph Percivalllinkedin.com/in/Percivall
> e: joeperciv...@yahoo.com
>
>
>
> On Friday, June 17, 2016 2:23 PM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com> wrote:
>
>
>
> 2009 is all done (including 0.x)
>
> Sent from my iPhone
>
>
> > On Jun 17, 2016, at 14:16, Joe Percivall <joeperciv...@yahoo.com.INVALID>
> wrote:
> >
> > Team,
> >
> > We are continuing to have good progress towards the 0.7.0 release.
> Tagged as "0.7.0" in Jira and still pending, we currently have 9 tickets
> that are all patch available.
> >
> > As a note, there seem to be a number of unversioned "patch available"
> tickets in Jira. I am going to take a look at them to see if any can easily
> make it into 0.7.0 (or are critical) but unless if they are critical I am
> not going to hold up the release for them.
> >
> > The current status for those tagged as 0.7.0:
> >
> > - "Processors could be started before the Controller Services that they
> depend on" NIFI-2032[1] [status] Critical bug that was added two days ago.
> Oleg Zhurakousky posted a PR and needs review.
> >
> >
> > - "Allow user to specify file filter regex when unpacking zip/tar
> archives" NI

Re: putTCP nifi 0.7?

[Joe Percivall]

Hello,


As a follow-up, the PutTCP processor was just merged into the master and 0.x 
branches and will be in the 0.7.0 release.
 Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Thursday, June 16, 2016 4:57 PM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Hello,

It is not currently marked as something that will go in 0.7.0 but I will review 
it to see where it stands. If it is able to be completed shortly (contributor 
addresses of my feedback) then it will make it in but if not then unfortunately 
it would slide to a later release.


This ticket falls into a category of unversioned "patch available" tickets 
(tickets that don't have a fix version and have a status "patch available") 
that need to be addressed. As the Release Manager for 0.7.0 I will take a look 
at the unversioned "patch available" tickets to see which of them can be 
finished off for 0.7.0 and ping the appropriate committers to help out.

Joe
- - - - - - Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com





On Thursday, June 16, 2016 2:00 PM, Ryan Ward <ryan.wa...@gmail.com> wrote:
Will this one make 0.7?

https://issues.apache.org/jira/browse/NIFI-1834

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

[Joe Percivall]

Team,

We are doing a great job finishing up tickets. Six more were closed over the 
weekend and most of the others made progress as well. We only have three more 
that are tagged as 0.7.0 in Jira. There are a couple others which are 
unversioned that are close but haven't been identified as important enough to 
hold up the release for so I will not reflect them here.

The current status for those left tagged as 0.7.0:

- "Processors could be started before the Controller Services that they depend 
on" NIFI-2032[1] [status] Oleg Zhurakousky's PR was looked at by Andy LoPresto 
but not clear if more action is needed. 

- "Create a processor to extract WAV file characteristics" NIFI-615[2] [status] 
Waiting for Joe Skora to rebase and put changes into a PR (which he said he 
would do today) and for final review from Joe Percivall (me) once the changes 
are made.

- "Create PutTCP Processor" NIFI-1834[3] [status] I took Matt Brown's original 
commit and applied my comments in another commit. Bryan Bende reviewed and I am 
addressing now.

Also NIFI-1974 and NIFI-1850 are marked as 0.7.0 and "Patch Available" in Jira 
but they are already merged into 0.x and work is being done to get it into 
master. I will not reflect them here.

[1] https://issues.apache.org/jira/browse/NIFI-2032
[2] https://issues.apache.org/jira/browse/NIFI-615

[3] https://issues.apache.org/jira/browse/NIFI-1834


Joe
- - - - - - 
Joseph Percivalllinkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Friday, June 17, 2016 2:23 PM, Oleg Zhurakousky 
<ozhurakou...@hortonworks.com> wrote:



2009 is all done (including 0.x)

Sent from my iPhone


> On Jun 17, 2016, at 14:16, Joe Percivall <joeperciv...@yahoo.com.INVALID> 
> wrote:
> 
> Team,
> 
> We are continuing to have good progress towards the 0.7.0 release. Tagged as 
> "0.7.0" in Jira and still pending, we currently have 9 tickets that are all 
> patch available. 
> 
> As a note, there seem to be a number of unversioned "patch available" tickets 
> in Jira. I am going to take a look at them to see if any can easily make it 
> into 0.7.0 (or are critical) but unless if they are critical I am not going 
> to hold up the release for them. 
> 
> The current status for those tagged as 0.7.0:
> 
> - "Processors could be started before the Controller Services that they 
> depend on" NIFI-2032[1] [status] Critical bug that was added two days ago. 
> Oleg Zhurakousky posted a PR and needs review.
> 
> 
> - "Allow user to specify file filter regex when unpacking zip/tar archives" 
> NIFI-1568[2] [status] Matt Burgess finished reviewing and is waiting for 
> Ricky Saltzer to address the final comment.
> 
> - "Create PutSlack processor" NIFI-1578 [3] [status] Matt Burgess found one 
> final issue before it is committed. Waiting for Adam Lamar to address.
> 
> -  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] [status] 
> Pierre Villard addressed Adam Taft's comments is waiting for a final review.
> 
> - "Support Custom Properties in Expression Language" NIFI-1974[5] [status] No 
> Change, waiting for Mark Payne to give a final review.
> 
> - "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
> variable "annotationData"" NIFI-2009[6] [status] Was merged into master but 
> needs to fix merge conflicts to be merged into 0.x
> - "Create a processor to extract WAV file characteristics" NIFI-615[7] 
> [status] Joe Skora posted a new branch addressing the comments but needs to 
> rebase and update PR. Branch needs final review from Joe Percivall (me)
> 
> - "Add SNMP processors" NIFI-1537[8] [status] PR is rebased and Oleg 
> Zhurakousky will be reviewing
> 
> - "Create FlowDebugger processor" NIFI-1829[9] [status] Joe Skora added 
> another commit and rebased. Tony won't be able to finalize review until the 
> weekend, Michael Moser volunteered to finish
> 
> 
> Also NiFi-1850 is marked as 0.7.0 and "Patch Available" in Jira but it was 
> already was merged into 0.x and work is being done to get it into master. I 
> will not reflect it here.
> 
> [1] https://issues.apache.org/jira/browse/NIFI-2032
> [2] https://issues.apache.org/jira/browse/NIFI-1568
> [3] https://issues.apache.org/jira/browse/NIFI-1578
> [4] https://issues.apache.org/jira/browse/NIFI-1620
> [5] https://issues.apache.org/jira/browse/NIFI-1974
> [6] https://issues.apache.org/jira/browse/NIFI-2009
> [7] https://issues.apache.org/jira/browse/NIFI-615
> [8] https://issues.apache.org/jira/browse/NIFI-1537
> [9] https://issues.apache.org/jira/browse/NIFI-1829
> 
> Joe
> - - - - - - 
> Joseph Percivalllinkedin.com/in/Percivall

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

[Joe Percivall]

Team,

We are continuing to have good progress towards the 0.7.0 release. Tagged as 
"0.7.0" in Jira and still pending, we currently have 9 tickets that are all 
patch available. 

As a note, there seem to be a number of unversioned "patch available" tickets 
in Jira. I am going to take a look at them to see if any can easily make it 
into 0.7.0 (or are critical) but unless if they are critical I am not going to 
hold up the release for them. 
 
The current status for those tagged as 0.7.0:

- "Processors could be started before the Controller Services that they depend 
on" NIFI-2032[1] [status] Critical bug that was added two days ago. Oleg 
Zhurakousky posted a PR and needs review.


- "Allow user to specify file filter regex when unpacking zip/tar archives" 
NIFI-1568[2] [status] Matt Burgess finished reviewing and is waiting for Ricky 
Saltzer to address the final comment.

- "Create PutSlack processor" NIFI-1578 [3] [status] Matt Burgess found one 
final issue before it is committed. Waiting for Adam Lamar to address.

-  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] [status] 
Pierre Villard addressed Adam Taft's comments is waiting for a final review.

- "Support Custom Properties in Expression Language" NIFI-1974[5] [status] No 
Change, waiting for Mark Payne to give a final review.

- "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
variable "annotationData"" NIFI-2009[6] [status] Was merged into master but 
needs to fix merge conflicts to be merged into 0.x
- "Create a processor to extract WAV file characteristics" NIFI-615[7] [status] 
Joe Skora posted a new branch addressing the comments but needs to rebase and 
update PR. Branch needs final review from Joe Percivall (me)

- "Add SNMP processors" NIFI-1537[8] [status] PR is rebased and Oleg 
Zhurakousky will be reviewing

- "Create FlowDebugger processor" NIFI-1829[9] [status] Joe Skora added another 
commit and rebased. Tony won't be able to finalize review until the weekend, 
Michael Moser volunteered to finish


Also NiFi-1850 is marked as 0.7.0 and "Patch Available" in Jira but it was 
already was merged into 0.x and work is being done to get it into master. I 
will not reflect it here.

[1] https://issues.apache.org/jira/browse/NIFI-2032
[2] https://issues.apache.org/jira/browse/NIFI-1568
[3] https://issues.apache.org/jira/browse/NIFI-1578
[4] https://issues.apache.org/jira/browse/NIFI-1620
[5] https://issues.apache.org/jira/browse/NIFI-1974
[6] https://issues.apache.org/jira/browse/NIFI-2009
[7] https://issues.apache.org/jira/browse/NIFI-615
[8] https://issues.apache.org/jira/browse/NIFI-1537
[9] https://issues.apache.org/jira/browse/NIFI-1829

Joe
- - - - - - 
Joseph Percivalllinkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Wednesday, June 15, 2016 10:56 AM, Joe Percivall 
<joeperciv...@yahoo.com.INVALID> wrote:
Team,

There was a lot of great progress yesterday, we closed or pushed 6 tickets. 
Also two tickets were added that are either critical or finishing shortly. The 
status of the remaining 12 tickets are below:

- "Corrupted flow file leads to a wedged flow" NIFI-2015[1] Added yesterday. 
Christopher McDermott, Mark Payne and Oleg Zhurakousky have been discussing the 
bug but no resolution yet.

- "Allow user to specify file filter regex when unpacking zip/tar archives" 
NIFI-1568[2] [status] Matt Burgess is continuing to review

- "Create PutSlack processor" NIFI-1578 [3] [status] Actively being worked on 
by contributor and reviewers

-  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] [status] No 
change since yesterday, still waiting for final review by Adam Taft. Commented 
asking if Adam would like me to finish the review

- "If unable to write to Content Repository, Process Session should 
automatically roll itself back" NIFI-1644[5] [status] No progress, commented 
asking Mark Payne (reporter) to see if it can slide.

- "Misconfigured MonitorMemory ReportingTask can not be stopped" NIFI-1690[6] 
[status] Actively being worked on by contributor and reviewer

- "Support Custom Properties in Expression Language" NIFI-1974[7] [status] New 
yesterday. Yolanda Davis submitted the PR and review by Mark Payne. Both are 
actively working on it.

- "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
variable "annotationData"" NIFI-2009[8] [status] +1 from committer, just 
waiting to be merged

- "Create a processor to extract WAV file characteristics" NIFI-615[9] [status] 
No change since yesterday, I will review. Needs rebase though

- "Add SNMP processors" NIFI-1537[10] [status] No significant change since 
yesterday, Oleg Zhurakousky is waiting for Pierre Villard to rebase.

- "Add option to bu

Re: putTCP nifi 0.7?

[Joe Percivall]

Hello,

It is not currently marked as something that will go in 0.7.0 but I will review 
it to see where it stands. If it is able to be completed shortly (contributor 
addresses of my feedback) then it will make it in but if not then unfortunately 
it would slide to a later release.


This ticket falls into a category of unversioned "patch available" tickets 
(tickets that don't have a fix version and have a status "patch available") 
that need to be addressed. As the Release Manager for 0.7.0 I will take a look 
at the unversioned "patch available" tickets to see which of them can be 
finished off for 0.7.0 and ping the appropriate committers to help out.

Joe
- - - - - - Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Thursday, June 16, 2016 2:00 PM, Ryan Ward  wrote:
Will this one make 0.7?

https://issues.apache.org/jira/browse/NIFI-1834

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

[Joe Percivall]

Team,

There was a lot of great progress yesterday, we closed or pushed 6 tickets. 
Also two tickets were added that are either critical or finishing shortly. The 
status of the remaining 12 tickets are below:

- "Corrupted flow file leads to a wedged flow" NIFI-2015[1] Added yesterday. 
Christopher McDermott, Mark Payne and Oleg Zhurakousky have been discussing the 
bug but no resolution yet.

- "Allow user to specify file filter regex when unpacking zip/tar archives" 
NIFI-1568[2] [status] Matt Burgess is continuing to review

- "Create PutSlack processor" NIFI-1578 [3] [status] Actively being worked on 
by contributor and reviewers

-  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] [status] No 
change since yesterday, still waiting for final review by Adam Taft. Commented 
asking if Adam would like me to finish the review

- "If unable to write to Content Repository, Process Session should 
automatically roll itself back" NIFI-1644[5] [status] No progress, commented 
asking Mark Payne (reporter) to see if it can slide.

- "Misconfigured MonitorMemory ReportingTask can not be stopped" NIFI-1690[6] 
[status] Actively being worked on by contributor and reviewer

- "Support Custom Properties in Expression Language" NIFI-1974[7] [status] New 
yesterday. Yolanda Davis submitted the PR and review by Mark Payne. Both are 
actively working on it.

- "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
variable "annotationData"" NIFI-2009[8] [status] +1 from committer, just 
waiting to be merged

- "Create a processor to extract WAV file characteristics" NIFI-615[9] [status] 
No change since yesterday, I will review. Needs rebase though

- "Add SNMP processors" NIFI-1537[10] [status] No significant change since 
yesterday, Oleg Zhurakousky is waiting for Pierre Villard to rebase.

- "Add option to bulk using Index or Update to PutElasticsearch" NIFI-1594[11] 
[status] João Henrique Ferreira de Freitas addressed Matt Burgess' comments and 
is waiting for final review by Matt

- "Create FlowDebugger processor" NIFI-1829[12] [status] Joe Skora added 
another commit and rebased. Tony won't be able to finalize review until the 
weekend, Michael Moser volunteered to finish

[1] https://issues.apache.org/jira/browse/NIFI-2015
[2] https://issues.apache.org/jira/browse/NIFI-1568
[3] https://issues.apache.org/jira/browse/NIFI-1578
[4] https://issues.apache.org/jira/browse/NIFI-1620
[5] https://issues.apache.org/jira/browse/NIFI-1644
[6] https://issues.apache.org/jira/browse/NIFI-1690
[7] https://issues.apache.org/jira/browse/NIFI-1974
[8] https://issues.apache.org/jira/browse/NIFI-2009
[9] https://issues.apache.org/jira/browse/NIFI-615
[10] https://issues.apache.org/jira/browse/NIFI-1537
[11] https://issues.apache.org/jira/browse/NIFI-1594
[12] https://issues.apache.org/jira/browse/NIFI-1829
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, June 14, 2016 7:11 PM, Andre  wrote:
Tony,

I second Joe's comments as well.

Since the early discussions about the branching model I have been under the
total impression that once 1.0 is released, 0.x would become support only
and updates restricted to critical issues (security & data-loss
break-fixes).

This is not to say that a NPE or a 100% CPU issue shouldn't be backported,
but I would imagine the effort to port to 0.x should be driven by the
contributor rather than the merger (as it is being done atm).


On Wed, Jun 15, 2016 at 8:13 AM, Joe Witt  wrote:

> According to the discussion we had about the management of the release
> lines there would only be incremental releases when something was critical
> enough (security or data loss).  And, if someone really wanted needed a
> minor release they could initiate and do that as well.  But as far as
> continued feature development and focus it would shift to 1.0.
>
> So emphasis moves to new major line but those staying on the old major can
> still have options as well.
> On Jun 14, 2016 5:31 PM, "Tony Kurc"  wrote:
>
> Joe, for some reason, my mental image was that I expected we'd keep
> releasing new 0.x minor releases for a while along with 1.x.
>
> Is that everyone else's expectations?
>

[DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

[Joe Percivall]

Team,

Things are closing in well but we need to get pretty specific on these to keep 
the release moving roughly along the lines of the schedule we've discussed 
previously.  Those of you who have tickets on here that can be moved to 1.0.0 
please do so.  Otherwise, let's please keep discussion/status information up so 
we can all see how we're trending toward release candidate readiness.

Below, I've explicitly outlined each person that is involved in each ticket so 
if you are on the hook for a ticket please help to get it closed out. There are 
a couple which have patches or PRs with no comments and need review, if able 
please help out the release by reviewing them.

The current items on the release based on JIRA fix version that remain are:

- "Cluster communication requires client certificates even if needClientAuth 
set to false" NIFI-1981[1] [status] PR created by Andy LoPresto.  NEEDS REVIEW.

- "Mock Framework allows processor to route to Relationships that the Processor 
does not support" NIFI-1152[2]
[status] Patch created by Puspendu Banerjee addressing Mark Payne's comments. 
Needs another round of review
 
- "Allow user to specify file filter regex when unpacking zip/tar archives" 
NIFI-1586[3] [status] Ricky Saltzer created a PR that addressed a couple 
comments and is rebased (request by Matt Burgess). Awaiting full review.

- "Create PutSlack processor" NIFI-1578 [4] [status] Adam Lamar pushed a new 
commit addressing comments. Awaiting review from Matt Burgess or Andy LoPresto. 

-  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[5] [status] 
Pierre Villard addressed Adam Taft's comments on the PR and is awaiting a final 
review.


- "If unable to write to Content Repository, Process Session should 
automatically roll itself back" NIFI-1644[6] [status] No progress, commented 
asking Mark Payne (reporter) to see if it can slide.

- "Misconfigured MonitorMemory ReportingTask can not be stopped" NIFI-1690[7] 
[status] Oleg Zhurakousky created a PR and is awaiting review.

- "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
variable "annotationData"" NIFI-2009[8] [status] No progress, commented asking 
Oleg Zhurakousky (assignee) to see if it can slide.

- "Create a processor to extract WAV file characteristics" NIFI-615[9] [status] 
PR submitted by Joe Skora, last comment addresses Joe Witt's concern's and is 
awaiting a full review.

- "Add SNMP processors" NIFI-1537[10] [status] Pierre Villard created a PR 
which addressed various comments, awaiting review from Oleg Zhurakousky.

- "Add option to bulk using Index or Update to PutElasticsearch" NIFI-1594[11] 
[status] João Henrique Ferreira de Freitas created a PR but needs to address 
Matt Burgess' comments.

- "Improve documentation regarding PropertyDescriptor name & displayName" 
NIFI-1795[12] [status] No progress, awaiting word from Andy LoPresto if it can 
slide

- "Create FlowDebugger processor" NIFI-1829[13] [status] Joe Skora created a PR 
and addressed review comments by Tony Kurc. Awaiting final review by Tony.

- "SplitJson enhancements for flowfile names and additional options" 
NIFI-1933[14] [status] Patch submitted by Alex Halldin. NEEDS REVIEW.

- "InferAvroSchema dynamically set record name" NIFI-1934[15] [status] Patch 
submitted by Alex Halldin. NEEDS REVIEW.

- "Added ConvertDynamicJsonToAvro processor" NIFI-1935[16] [status] Patch 
submitted by Alex Halldin. Currently being commented on by Bryan Bende and Joe 
Witt on master vs 0.x branch but needs a full review.
 

[1] https://issues.apache.org/jira/browse/NIFI-1981
[2] https://issues.apache.org/jira/browse/NIFI-1152
[3] https://issues.apache.org/jira/browse/NIFI-1568
[4] https://issues.apache.org/jira/browse/NIFI-1578
[5] https://issues.apache.org/jira/browse/NIFI-1620
[6] https://issues.apache.org/jira/browse/NIFI-1644
[7] https://issues.apache.org/jira/browse/NIFI-1690
[8] https://issues.apache.org/jira/browse/NIFI-2009
[9] https://issues.apache.org/jira/browse/NIFI-615
[10] https://issues.apache.org/jira/browse/NIFI-1537
[11] https://issues.apache.org/jira/browse/NIFI-1594
[12] https://issues.apache.org/jira/browse/NIFI-1795
[13] https://issues.apache.org/jira/browse/NIFI-1829
[14] https://issues.apache.org/jira/browse/NIFI-1933
[15] https://issues.apache.org/jira/browse/NIFI-1934
[16] https://issues.apache.org/jira/browse/NIFI-1935

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com

Re: Apache NiFi 0.7.0 Release date ?

[Joe Percivall]

Looks like time to start finishing up the remaining 17 tickets and getting 
together a release. I will volunteer to be Release Manager. I'll start another 
email thread outlining the remaining tickets and their statuses.
 
Joe
- - - - - - Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com




On Tuesday, June 7, 2016 11:26 AM, Matt Burgess  wrote:
There was a whitespace issue in the test HL7 file. Joey moved the
content into the test class itself and removed the file. I reviewed
and merged to 0.x and master, so things should be back to normal.
Sorry for the hiccup.

Regards,
Matt


On Tue, Jun 7, 2016 at 10:03 AM, Matt Burgess  wrote:
> I merged an HL7 PR last night, I will take a look. The tests passed
> for me but maybe I screwed something up with the patch application.
>
> On Tue, Jun 7, 2016 at 10:00 AM, Andre  wrote:
>> + 1 on the build errors on HL7.
>>
>> Seems to break things in here as well.
>>
>> Cheers
>>
>> On Tue, Jun 7, 2016 at 11:58 PM, Ryan H  wrote:
>>
>>> I did build the 0.x branch for the latest 0.7.0... It works when you skip
>>> building the tests.
>>>

Re: [discuss] Proposed addition of replaceRegex to expression language

[Joe Percivall]

Andy,

Nice write-up and thanks for bringing attention to this. I definitely assumed 
for a while that replace vs replaceAll was the number of things replaced. The 
underlying problem, I think, is that these EL methods are just wrappers around 
the Java String methods and the Java String methods are named in a confusing 
manner. 
 
I am on board with adding a "replaceFirst(regex, replacement)" method. This 
adds a bit more functionality and is just exposing another Java String method.

In addition to that, I would suggest doing something to alleviate the confusion 
between "replace" and "replaceAll". In a similar fashion to adding decimal 
support, I see two avenues we could take:

1. Change the names of the functions to "replaceLiteral" and "replaceRegex" (or 
"replaceAllLiteral" and "replaceAllRegex")
2. Remove one of the methods and add a third field to the remaining method to 
indicate whether to replace literally or interpret as a regex

Both of these would be breaking changes and introduced with 1.0 and I am 
leaning towards option 1 with the base name "replace". I believe when the 
"replaceFirst" method is added, "replaceLiteral" and "replaceRegex" would be 
easy to understand that they replace all occurrences.

Joe

- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com



On Wednesday, May 25, 2016 6:24 PM, Andy LoPresto  wrote:



Hi all,

During investigation of an expression language issue posted to the list, I 
discovered that replace explicitly delegates to a String#replace invocation 
that only accepts literal expressions, not regular expressions, while 
replaceAll accepts regular expressions. I thought this was an oversight and 
filed NIFI-1919 [1] to document and fix this, by changing the ReplaceEvaluator 
[2] to use String#replaceFirst, which accepts regular expressions. I wrote 
failing unit tests [3] to capture the fix. After implementing the change, two 
existing unit tests [4] broke, which indicated a regression. At first, I 
believed these two tests to be incorrect, but further investigation showed they 
were merely surprising. 

TestQuery#testQuotingQuotes (below) fails on the second verifyEquals call, but 
the test is asserting that replace should replace multiple instances of the 
single quote. While this is similar to String#replace, because the expression 
language exposes only two methods — replace vs. replaceAll — one could easily 
assume the difference between the two was the number of attempted replacements, 
rather than the actual difference, which is literal expression vs. pattern. 

@Test
public void testQuotingQuotes() {
final Map attributes = new HashMap<>();
attributes.put("xx", "say 'hi'");

String query = "${xx:replaceAll( \"'.*'\", '\\\"hello\\\"' )}";
verifyEquals(query, attributes, "say \"hello\"");

query = "${xx:replace( \"'\", '\"')}";
verifyEquals(query, attributes, "say \"hi\"");

query = "${xx:replace( '\\'', '\"')}";
System.out.println(query);
verifyEquals(query, attributes, "say \"hi\"");
}
TestQuery#testReplaceAllWithOddNumberOfBackslashPairs (below) also fails on the 
first verifyEquals call with a PatternSyntaxException. I am investigating that 
further.

@Test
public void testReplaceAllWithOddNumberOfBackslashPairs() {
final Map attributes = new HashMap<>();
attributes.put("filename", "C:\\temp\\.txt");

verifyEquals("${filename:replace('', '/')}", attributes, "C:/temp/.txt");
verifyEquals("${filename:replaceAll('', '/')}", attributes, 
"C:/temp/.txt");
verifyEquals("${filename:replaceAll('\\.txt$', '')}", attributes, 
"C:\\temp");
}
While I originally had just modified replace, after looking at the EL 
documentation [5], replace is explicitly documented to only replace literal 
expressions, and does so multiple times, as does Java’s String#replace [6]. I 
now propose to add another method replaceFirst, which accepts a pattern and 
replaces only the first occurrence. I will update the unit tests to properly 
capture this, and will update the documentation to reflect the new method. 

Thoughts from the community?

[1] https://issues.apache.org/jira/browse/NIFI-1919
[2] 
https://github.com/alopresto/nifi/blob/NIFI-1919/nifi-commons/nifi-expression-language/src/main/java/org/apache/nifi/attribute/expression/language/evaluation/functions/ReplaceEvaluator.java
[3] 
https://github.com/alopresto/nifi/blob/NIFI-1919/nifi-commons/nifi-expression-language/src/test/groovy/org/apache/nifi/attribute/expression/language/QueryGroovyTest.groovy
[4] 
https://github.com/alopresto/nifi/blob/NIFI-1919/nifi-commons/nifi-expression-language/src/test/java/org/apache/nifi/attribute/expression/language/TestQuery.java
[5] 
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#replace
[6] 
https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#replace(java.lang.CharSequence,%20java.lang.CharSequence)



Andy LoPresto
alopre...@apache.org