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: [VOTE] Release Apache NiFi 1.0.0 (RC1)

[Andre]

Tony,

I tend to agree with your view but I was under the impression the proposed
change does not make changes to NiFi itself?

Correct me if I am wrong - maven still feels quite cryptic to me - but my
understanding was that the PR only configures tests to be ran with a
particular variable java option "-Djava.awt.headless=true" (via a
configuration of the surefire plugin within the master pom.xml)?

It may be just me, but I have a feeling the result would be the testing
phase being more deterministic, reducing the importance of environment
components in the build / test process?

Having said that, happy to go with what the team finds better

Cheers

On Tue, Aug 30, 2016 at 11:53 AM, Tony Kurc  wrote:

> Andre,
> I've been reluctant to do a software change for something that is,
> debatably an environment issue. If DISPLAY is set, I would think one would
> be reasonably assured one had an x server.
>
> On Mon, Aug 29, 2016 at 8:02 PM, Andre  wrote:
>
> > Tony,
> >
> > Yes. That happens when the JDK is not headless. I submitted a PR that
> > forces maven to run in headless mode which also solves the issue.
> >
> > Have you had a chance to check https://github.com/apache/nifi/pull/961 ?
> >
> > Cheers
> >
> > On Tue, Aug 30, 2016 at 9:57 AM, Tony Kurc  wrote:
> >
> > > Andre, on the X11 issue, it can occur if you have the DISPLAY
> environment
> > > variable set, but no X server.
> > >
> > > I reported it a while back with what got me past it:
> > > https://issues.apache.org/jira/browse/NIFI-1154
> > >
> > > On Aug 29, 2016 11:00 AM, "Yolanda Davis" 
> > > wrote:
> > >
> > > > Resending on appropriate thread:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Ran full test suite, with rat and contrib-check.  Verified, readme,
> > > notice,
> > > > license, commit ID, hashes and checksums. Tested flows and templates
> in
> > > > standalone cluster (on Mac OS).
> > > >
> > > > On Fri, Aug 26, 2016 at 12:25 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.
> > > > >
> > > > > The source zip, including signatures, digests, etc. can be found
> at:
> > > > > https://repository.apache.org/content/repositories/orgapache
> > nifi-1090/
> > > > >
> > > > > Note: There is a second binary being distributed now, the NiFi
> > Toolkit.
> > > > It
> > > > > can be used to facilitate securing a NiFi instance.
> > > > >
> > > > > The Git tag is nifi-1.0.0-RC1
> > > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
> > d5ed9667
> > > > > 1d3c581707
> > > > >
> > > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > > SHA256: 22167ede5127683ca8de6dbd2fb911
> 2cb1de650b7cfff7e640c905521447
> > > af92
> > > > >
> > > > > 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
> > > > >
> > > > > 595 issues were closed/resolved for this release:
> > > > > 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
> > > > >
> > > > > 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
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > > Thanks!
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > yolanda.m.da...@gmail.com
> > > > @YolandaMDavis
> > > >
> > >
> >
>

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

[Aldrin Piri]

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  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c gen_uuid.c  -o gen_uuid.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c isnull.c  -o isnull.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c pack.c  -o pack.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c parse.c  -o parse.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c unpack.c  -o unpack.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c unparse.c  -o unparse.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > > -fvisibility=hidden -fPIC -I.. -c uuid_time.c  -o uuid_time.o
> > > clang: warning: argument unused during compilation: '-rdynamic'
> > >
> > > ...
> > >
> > >
> > > src/FlowController.cpp:83:7: warning: unused variable 'flow_full_path'
> > > [-Wunused-variable]
> > > char flow_full_path[PATH_MAX];
> > >  ^

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

[Andrew Psaltis]

+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  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c gen_uuid.c  -o gen_uuid.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c isnull.c  -o isnull.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c pack.c  -o pack.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c parse.c  -o parse.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c unpack.c  -o unpack.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c unparse.c  -o unparse.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> > gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> > -fvisibility=hidden -fPIC -I.. -c uuid_time.c  -o uuid_time.o
> > clang: warning: argument unused during compilation: '-rdynamic'
> >
> > ...
> >
> >
> > src/FlowController.cpp:83:7: warning: unused variable 'flow_full_path'
> > [-Wunused-variable]
> > char flow_full_path[PATH_MAX];
> >  ^
> > src/FlowController.cpp:82:8: warning: unused variable 'flowPath'
> > [-Wunused-variable]
> > char *flowPath = NULL;
> >   ^
> > 2 warnings generated.
> >
> > ...
> >
> >
> > g++ -Os -fexceptions -fpermissive -Wno-write-strings -std=c++11 -fPIC
> > -Wall -g -Wno-unused-private-field -I./inc -I./src -I./test
> -I./thirdparty
> > -I/usr/include/libxml2 -I./thirdparty/yaml-cpp-yaml-cpp-0.5.3/include -o
> > ./build/Server test/Server.cpp -L./build -L./thirdparty/uuid
> > -L./thirdparty/yaml-cpp-yaml-cpp-0.5.3/lib/ -lminifi -lxml2 -pthread
> > -luuid -lyaml-cpp
> > clang: error: no such file or directory: 'test/Server.cpp'
> > make: [tests] Error 1 (ignored)
> >
> > In minifi.properties (is there a reason this is nifi.version instead of
> > minifi.version?):
> >
> > # Core Properties #
> > nifi.version=0.0.1
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Aug 29, 2016, at 4:47 PM, Koji Kawamura 
> wrote:
> >
> > +1 (non-binding)
> >

Re: Request for enhancement

[Gunjan Dave]

Hi Joe, I dont seem to have access to nifi jira to create one. Can it be
given? Or if not, could someone help raising it.

On Tue, Aug 30, 2016, 7:49 AM Joe Percivall  wrote:

> - 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 <
> gunjanpiyushd...@gmail.com> 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)

[Tony Kurc]

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  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c gen_uuid.c  -o gen_uuid.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c isnull.c  -o isnull.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c pack.c  -o pack.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c parse.c  -o parse.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c unpack.c  -o unpack.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c unparse.c  -o unparse.o
> clang: warning: argument unused during compilation: '-rdynamic'
> gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings
> -fvisibility=hidden -fPIC -I.. -c uuid_time.c  -o uuid_time.o
> clang: warning: argument unused during compilation: '-rdynamic'
>
> ...
>
>
> src/FlowController.cpp:83:7: warning: unused variable 'flow_full_path'
> [-Wunused-variable]
> char flow_full_path[PATH_MAX];
>  ^
> src/FlowController.cpp:82:8: warning: unused variable 'flowPath'
> [-Wunused-variable]
> char *flowPath = NULL;
>   ^
> 2 warnings generated.
>
> ...
>
>
> g++ -Os -fexceptions -fpermissive -Wno-write-strings -std=c++11 -fPIC
> -Wall -g -Wno-unused-private-field -I./inc -I./src -I./test -I./thirdparty
> -I/usr/include/libxml2 -I./thirdparty/yaml-cpp-yaml-cpp-0.5.3/include -o
> ./build/Server test/Server.cpp -L./build -L./thirdparty/uuid
> -L./thirdparty/yaml-cpp-yaml-cpp-0.5.3/lib/ -lminifi -lxml2 -pthread
> -luuid -lyaml-cpp
> clang: error: no such file or directory: 'test/Server.cpp'
> make: [tests] Error 1 (ignored)
>
> In minifi.properties (is there a reason this is nifi.version instead of
> minifi.version?):
>
> # Core Properties #
> nifi.version=0.0.1
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Aug 29, 2016, at 4:47 PM, Koji Kawamura  wrote:
>
> +1 (non-binding)
>
> Downloaded the source archive, verified signature, md5, sha1, and
> sha256 hashes are all good.
> LICENSE file looks good
> Built the source successfully with the steps written in README, on Mac
> OS X El Captain
> Used brew to install boost: $ brew install boost
> Created conf/flow.yml:
> - copy & paste from README
> - modified Input Ports id so that it matches with the remote NiFi's
> input port uuid
> - enabled Site-to-Site at the remote NiFi
> Started minifi, created a file under /tmp/getfile dir, then confirmed
> the file content was sent to the remote NiFi via Site-to-Site
>
>
>
> On Mon, Aug 29, 2016 at 5:52 AM, 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:
>

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)

[Andy LoPresto]

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  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c gen_uuid.c  -o gen_uuid.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c isnull.c  -o isnull.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c pack.c  -o pack.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c parse.c  -o parse.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c unpack.c  -o unpack.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c unparse.c  -o unparse.o
clang: warning: argument unused during compilation: '-rdynamic'
gcc -g -Wall -rdynamic  -O0 -ggdb -g3 -fexceptions -Wno-write-strings 
-fvisibility=hidden -fPIC -I.. -c uuid_time.c  -o uuid_time.o
clang: warning: argument unused during compilation: '-rdynamic'

...


src/FlowController.cpp:83:7: warning: unused variable 'flow_full_path' 
[-Wunused-variable]
char flow_full_path[PATH_MAX];
 ^
src/FlowController.cpp:82:8: warning: unused variable 'flowPath' 
[-Wunused-variable]
char *flowPath = NULL;
  ^
2 warnings generated.

...


g++ -Os -fexceptions -fpermissive -Wno-write-strings -std=c++11 -fPIC -Wall -g 
-Wno-unused-private-field -I./inc -I./src -I./test -I./thirdparty 
-I/usr/include/libxml2 -I./thirdparty/yaml-cpp-yaml-cpp-0.5.3/include -o 
./build/Server test/Server.cpp -L./build -L./thirdparty/uuid 
-L./thirdparty/yaml-cpp-yaml-cpp-0.5.3/lib/ -lminifi -lxml2 -pthread -luuid 
-lyaml-cpp
clang: error: no such file or directory: 'test/Server.cpp'
make: [tests] Error 1 (ignored)

In minifi.properties (is there a reason this is nifi.version instead of 
minifi.version?):

# Core Properties #
nifi.version=0.0.1

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

> On Aug 29, 2016, at 4:47 PM, Koji Kawamura  wrote:
> 
> +1 (non-binding)
> 
> Downloaded the source archive, verified signature, md5, sha1, and
> sha256 hashes are all good.
> LICENSE file looks good
> Built the source successfully with the steps written in README, on Mac
> OS X El Captain
> Used brew to install boost: $ brew install boost
> Created conf/flow.yml:
> - copy & paste from README
> - modified Input Ports id so that it matches with the remote NiFi's
> input port uuid
> - enabled Site-to-Site at the remote NiFi
> Started minifi, created a file under /tmp/getfile dir, then confirmed
> the file content was sent to the remote NiFi via Site-to-Site
> 
> 
> 
> On Mon, Aug 29, 2016 at 5:52 AM, 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:
>>
>> 

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

[Tony Kurc]

Andre,
I've been reluctant to do a software change for something that is,
debatably an environment issue. If DISPLAY is set, I would think one would
be reasonably assured one had an x server.

On Mon, Aug 29, 2016 at 8:02 PM, Andre  wrote:

> Tony,
>
> Yes. That happens when the JDK is not headless. I submitted a PR that
> forces maven to run in headless mode which also solves the issue.
>
> Have you had a chance to check https://github.com/apache/nifi/pull/961 ?
>
> Cheers
>
> On Tue, Aug 30, 2016 at 9:57 AM, Tony Kurc  wrote:
>
> > Andre, on the X11 issue, it can occur if you have the DISPLAY environment
> > variable set, but no X server.
> >
> > I reported it a while back with what got me past it:
> > https://issues.apache.org/jira/browse/NIFI-1154
> >
> > On Aug 29, 2016 11:00 AM, "Yolanda Davis" 
> > wrote:
> >
> > > Resending on appropriate thread:
> > >
> > > +1 (non-binding)
> > >
> > > Ran full test suite, with rat and contrib-check.  Verified, readme,
> > notice,
> > > license, commit ID, hashes and checksums. Tested flows and templates in
> > > standalone cluster (on Mac OS).
> > >
> > > On Fri, Aug 26, 2016 at 12:25 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.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/orgapache
> nifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
> d5ed9667
> > > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> > af92
> > > >
> > > > 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
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > 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
> > > >
> > > > 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
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > > >
> > >
> > >
> > >
> > > --
> > > --
> > > yolanda.m.da...@gmail.com
> > > @YolandaMDavis
> > >
> >
>

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: [VOTE] Release Apache NiFi MiNiFI C++ 0.0.1 (RC1)

[Tony Kurc]

All,
Question about the LICENSE file, I didn't see gmock
(thirdparty/yaml-cpp-yaml-cpp-0.5.3/test/gmock-1.7.0) listed in the LICENSE
, is this because it is "bundled" with yaml-cpp?

Tony

On Mon, Aug 29, 2016 at 9:34 PM, 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: c72046d86a9dc34033fa40ad1b2300f1f7915acd369f763e7fc02095d09b
>> b91e
>> >
>> > 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: [VOTE] Release Apache NiFi MiNiFI C++ 0.0.1 (RC1)

[Tony Kurc]

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 
 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)

[Andre]

Tony,

Yes. That happens when the JDK is not headless. I submitted a PR that
forces maven to run in headless mode which also solves the issue.

Have you had a chance to check https://github.com/apache/nifi/pull/961 ?

Cheers

On Tue, Aug 30, 2016 at 9:57 AM, Tony Kurc  wrote:

> Andre, on the X11 issue, it can occur if you have the DISPLAY environment
> variable set, but no X server.
>
> I reported it a while back with what got me past it:
> https://issues.apache.org/jira/browse/NIFI-1154
>
> On Aug 29, 2016 11:00 AM, "Yolanda Davis" 
> wrote:
>
> > Resending on appropriate thread:
> >
> > +1 (non-binding)
> >
> > Ran full test suite, with rat and contrib-check.  Verified, readme,
> notice,
> > license, commit ID, hashes and checksums. Tested flows and templates in
> > standalone cluster (on Mac OS).
> >
> > On Fri, Aug 26, 2016 at 12:25 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.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> af92
> > >
> > > 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
> > >
> > > 595 issues were closed/resolved for this release:
> > > 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
> > >
> > > 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
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> >
> >
> >
> > --
> > --
> > yolanda.m.da...@gmail.com
> > @YolandaMDavis
> >
>

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

[Tony Kurc]

Andre, on the X11 issue, it can occur if you have the DISPLAY environment
variable set, but no X server.

I reported it a while back with what got me past it:
https://issues.apache.org/jira/browse/NIFI-1154

On Aug 29, 2016 11:00 AM, "Yolanda Davis"  wrote:

> Resending on appropriate thread:
>
> +1 (non-binding)
>
> Ran full test suite, with rat and contrib-check.  Verified, readme, notice,
> license, commit ID, hashes and checksums. Tested flows and templates in
> standalone cluster (on Mac OS).
>
> On Fri, Aug 26, 2016 at 12:25 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.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> >
> > Note: There is a second binary being distributed now, the NiFi Toolkit.
> It
> > can be used to facilitate securing a NiFi instance.
> >
> > The Git tag is nifi-1.0.0-RC1
> > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > 1d3c581707
> >
> > Checksums of nifi-1.0.0-source-release.zip:
> > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> >
> > 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
> >
> > 595 issues were closed/resolved for this release:
> > 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
> >
> > 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
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
>
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>

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

[Pierre Villard]

Forgot one minor remark:
If I connect via SSH to my VM and call './minifi.sh stop' when minifi.sh is
already stopped, I get disconnected from the VM and cannot reconnect it
unless I reboot the VM.

I opened a JIRA: https://issues.apache.org/jira/browse/MINIFI-97

2016-08-29 23:45 GMT+02:00 Pierre Villard :

> +1 (non-binding) release this package as nifi-minifi-cpp-0.0.1
>
> - verified signatures, hashes, and LICENSE/NOTICE/README
> - built sources on CentOS 7 and ran a GenerateFlowFile -> RPG ->
> Standalone NiFi
>
> Remark:
> - in the readme, the requirement "libboost" is "boost" on CentOS 7, I
> don't know if it is OS dependent.
>
>
> 2016-08-29 20:37 GMT+02:00 Bryan Bende :
>
>> +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: c72046d86a9dc34033fa40ad1b2300f1f7915acd369f763e7fc02095d09b
>> b91e
>> >
>> > 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: [VOTE] Release Apache NiFi MiNiFI C++ 0.0.1 (RC1)

[Pierre Villard]

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

- verified signatures, hashes, and LICENSE/NOTICE/README
- built sources on CentOS 7 and ran a GenerateFlowFile -> RPG -> Standalone
NiFi

Remark:
- in the readme, the requirement "libboost" is "boost" on CentOS 7, I don't
know if it is OS dependent.


2016-08-29 20:37 GMT+02:00 Bryan Bende :

> +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: [VOTE] Release Apache NiFi 1.0.0 (RC1)

[Alan Jackoway]

Builds with JDK 1.8.0_60 so I am a +0 in total. It's been a long time
(maybe 0.5?) since I attempted a full nifi build rather than just building
the processors I am working with. It seems like some time in that window a
JDK incompatibility was introduced.

On Mon, Aug 29, 2016 at 2:58 PM, Alan Jackoway  wrote:

> -1 (non-binding) from me, but likely an issue on my machine.
>
> I get a compile error in nifi-framework-cluster on this release and master
> using an empty maven repository.
>
> Mac OS X 10.10.5. Maven 3.2.5. Oracle Java 1.8.0_31
>
> The end of maven debug output (which doesn't even say which file is
> failing to compile) is at https://gist.github.com/jackowaya/
> 25a8f184089335b1eed14f00cbb5f36b if you're interested.
>
> I'm going to try a more recent JDK next.
>
> Alan
>
> On Mon, Aug 29, 2016 at 2:38 PM, Jeff  wrote:
>
>> Still voting a +1 for the release, but I recently created two JIRAs for
>> the
>> issues I encountered while testing nifi-1.0.0-RC1:
>>
>> https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
>> should include more information
>> https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
>> response timeouts in cluster
>>
>> On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman 
>> wrote:
>>
>> > +1 (binding)
>> >
>> > Verified keys, hashes, build, etc. Ran standalone and cluster secured
>> > instances.
>> >
>> > Evaluated the issues Koji reported and created two minor JIRAs [1] [2]
>> to
>> > perform some additional clean up in the next release.
>> >
>> > Thanks, Joe P!
>> >
>> > Matt
>> >
>> > [1] https://issues.apache.org/jira/browse/NIFI-2694
>> > [2] https://issues.apache.org/jira/browse/NIFI-2697
>> >
>> > On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne 
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Verified the keys & md5 hash. Was able to startup the node and verify
>> > > things are behaving as expected.
>> > > Verified that the README, NOTICE, and LICENSE files exist and appear
>> to
>> > be
>> > > correct.
>> > >
>> > > Thanks for pulling this together, Joe P!
>> > >
>> > > > On Aug 26, 2016, at 12:25 PM, Joe Percivall > > .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.
>> > > >
>> > > > The source zip, including signatures, digests, etc. can be found at:
>> > > > https://repository.apache.org/content/repositories/orgapache
>> nifi-1090/
>> > > >
>> > > > Note: There is a second binary being distributed now, the NiFi
>> Toolkit.
>> > > It
>> > > > can be used to facilitate securing a NiFi instance.
>> > > >
>> > > > The Git tag is nifi-1.0.0-RC1
>> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
>> d5ed9667
>> > > 1d3c581707
>> > > >
>> > > > Checksums of nifi-1.0.0-source-release.zip:
>> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
>> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
>> > > > SHA256:
>> > 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>> > > >
>> > > > 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
>> > > >
>> > > > 595 issues were closed/resolved for this release:
>> > > > 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
>> > > >
>> > > > 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
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 Do not release this package because...
>> > > >
>> > > > Thanks!
>> > >
>> > >
>> >
>>
>
>

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

[Alan Jackoway]

-1 (non-binding) from me, but likely an issue on my machine.

I get a compile error in nifi-framework-cluster on this release and master
using an empty maven repository.

Mac OS X 10.10.5. Maven 3.2.5. Oracle Java 1.8.0_31

The end of maven debug output (which doesn't even say which file is failing
to compile) is at
https://gist.github.com/jackowaya/25a8f184089335b1eed14f00cbb5f36b if
you're interested.

I'm going to try a more recent JDK next.

Alan

On Mon, Aug 29, 2016 at 2:38 PM, Jeff  wrote:

> Still voting a +1 for the release, but I recently created two JIRAs for the
> issues I encountered while testing nifi-1.0.0-RC1:
>
> https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
> should include more information
> https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
> response timeouts in cluster
>
> On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman 
> wrote:
>
> > +1 (binding)
> >
> > Verified keys, hashes, build, etc. Ran standalone and cluster secured
> > instances.
> >
> > Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
> > perform some additional clean up in the next release.
> >
> > Thanks, Joe P!
> >
> > Matt
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-2694
> > [2] https://issues.apache.org/jira/browse/NIFI-2697
> >
> > On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Verified the keys & md5 hash. Was able to startup the node and verify
> > > things are behaving as expected.
> > > Verified that the README, NOTICE, and LICENSE files exist and appear to
> > be
> > > correct.
> > >
> > > Thanks for pulling this together, Joe P!
> > >
> > > > On Aug 26, 2016, at 12:25 PM, Joe Percivall  > .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.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/
> 74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256:
> > 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> > > >
> > > > 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
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > 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
> > > >
> > > > 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
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > >
> > >
> >
>

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

[Jeff]

Still voting a +1 for the release, but I recently created two JIRAs for the
issues I encountered while testing nifi-1.0.0-RC1:

https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
should include more information
https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
response timeouts in cluster

On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman  wrote:

> +1 (binding)
>
> Verified keys, hashes, build, etc. Ran standalone and cluster secured
> instances.
>
> Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
> perform some additional clean up in the next release.
>
> Thanks, Joe P!
>
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-2694
> [2] https://issues.apache.org/jira/browse/NIFI-2697
>
> On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne  wrote:
>
> > +1 (binding)
> >
> > Verified the keys & md5 hash. Was able to startup the node and verify
> > things are behaving as expected.
> > Verified that the README, NOTICE, and LICENSE files exist and appear to
> be
> > correct.
> >
> > Thanks for pulling this together, Joe P!
> >
> > > On Aug 26, 2016, at 12:25 PM, Joe Percivall  .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.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256:
> 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> > >
> > > 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
> > >
> > > 595 issues were closed/resolved for this release:
> > > 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
> > >
> > > 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
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> >
> >
>

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

[Bryan Bende]

+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: [VOTE] Release Apache NiFi 1.0.0 (RC1)

[Matt Gilman]

+1 (binding)

Verified keys, hashes, build, etc. Ran standalone and cluster secured
instances.

Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
perform some additional clean up in the next release.

Thanks, Joe P!

Matt

[1] https://issues.apache.org/jira/browse/NIFI-2694
[2] https://issues.apache.org/jira/browse/NIFI-2697

On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne  wrote:

> +1 (binding)
>
> Verified the keys & md5 hash. Was able to startup the node and verify
> things are behaving as expected.
> Verified that the README, NOTICE, and LICENSE files exist and appear to be
> correct.
>
> Thanks for pulling this together, Joe P!
>
> > On Aug 26, 2016, at 12:25 PM, Joe Percivall 
> wrote:
> >
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi,
> > nifi-1.0.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> >
> > Note: There is a second binary being distributed now, the NiFi Toolkit.
> It
> > can be used to facilitate securing a NiFi instance.
> >
> > The Git tag is nifi-1.0.0-RC1
> > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
> >
> > Checksums of nifi-1.0.0-source-release.zip:
> > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> >
> > 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
> >
> > 595 issues were closed/resolved for this release:
> > 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
> >
> > 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
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
>
>

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

[Mark Payne]

+1 (binding)

Verified the keys & md5 hash. Was able to startup the node and verify things 
are behaving as expected.
Verified that the README, NOTICE, and LICENSE files exist and appear to be 
correct.

Thanks for pulling this together, Joe P!

> On Aug 26, 2016, at 12:25 PM, Joe Percivall  
> wrote:
> 
> Hello Apache NiFi Community,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
> 
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
> 
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * 
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
> * 
> https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
> 
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> 
> 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
> 
> 595 issues were closed/resolved for this release:
> 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
> 
> 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
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
> 
> Thanks!

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

[Jeff]

+1 (non-binding) Release this package as nifi-1.0.0

- Verified checksums, signature, LICENSE/NOTICE/README
- Built source with contrib-check
- Tested standalone and clustered instances

There were two issues that I ran into that are minor and are
user-experience-based.  The first issue encountered was while trying to
create a template on a clustered instance.  After selecting multiple
components that included a process group to which I had read permissions,
the "Create Template" icon was enabled.  However, the UI informed me that I
did not have sufficient permissions to create the template.  There was a
controller service in a child process group to which I did not have read
access, which was the cause of the insufficient privileges.  After
providing myself read access to that controller service, I was able to
create the template, and import it on a standalone instance.  In this case,
the code is doing what it should, however from a user experience
perspective, it may be difficult for the user to deduce why the template
cannot be created.

The second issue I encountered was during the debugging I did to figure out
why the template couldn't be created.  When running as a cluster, if a node
is unable to respond within the socket timeout (eg, hitting a breakpoint
while debugging), an IllegalStateException will be thrown that causes the
UI to show the "check config and fix errors" page.  Once the breakpoint in
the code is passed, the UI can be reloaded and the cluster recovers from
the timeout without any user intervention at the service level.  I don't
think there's a bug here, but the user experience could be improved.  If a
user initiates a replicated request to a node that is unable to respond
within the socket timeout duration, the user might think NiFi crashed, when
it in fact didn't.

On Mon, Aug 29, 2016 at 11:29 AM Bryan Bende  wrote:

> +1 (binding) Release this package as nifi-1.0.0
>
> - Verified checksums, signature, commit hash, and LICENSE/NOTICE/README
> - Performed full build with contrib-check
> - Tested a standalone unsecure instance and then used the toolkit to create
> a secure cluster
>
> On Mon, Aug 29, 2016 at 11:00 AM, Yolanda Davis  >
> wrote:
>
> > Resending on appropriate thread:
> >
> > +1 (non-binding)
> >
> > Ran full test suite, with rat and contrib-check.  Verified, readme,
> notice,
> > license, commit ID, hashes and checksums. Tested flows and templates in
> > standalone cluster (on Mac OS).
> >
> > On Fri, Aug 26, 2016 at 12:25 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.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256:
> 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> > >
> > > 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
> > >
> > > 595 issues were closed/resolved for this release:
> > > 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
> > >
> > > 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
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> >
> >
> >
> > --
> > --
> > yolanda.m.da...@gmail.com
> > @YolandaMDavis
> >
>

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

[Joey Frazee]

+1 (non-binding)

- Verified checksums, signature, and commit hash
- Ran build on OS X with all tests and contrib-check
- Tested recent ExtractHL7Attributes (NIFI-2564) and TransformXml (NIFI-2142) 
improvements, and template import/export on an unsecured cluster with external 
ZK
On Aug 26, 2016, at 11:29 AM, Joe Percivall  
wrote:

Hello Apache NiFi Community,

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

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

Note: There is a second binary being distributed now, the NiFi Toolkit. It
can be used to facilitate securing a NiFi instance.

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

Checksums of nifi-1.0.0-source-release.zip:
MD5: 8bdba49a73b94d036fad6c63b0ebe39d
SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92

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

595 issues were closed/resolved for this release:
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

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
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!

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

[Aldrin Piri]

+1, binding

Hashes check out
Signature looks good
Build looked good and ran on OS X, CentOS, Debian
Sample flows from templates check out and look good.

Only small hangup was none of the  TestListenSMTP tests passing in Windows
10 as created but worked with relaxed timeouts. Created a JIRA issue [1]

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

On Mon, Aug 29, 2016 at 11:28 AM, Bryan Bende  wrote:

> +1 (binding) Release this package as nifi-1.0.0
>
> - Verified checksums, signature, commit hash, and LICENSE/NOTICE/README
> - Performed full build with contrib-check
> - Tested a standalone unsecure instance and then used the toolkit to create
> a secure cluster
>
> On Mon, Aug 29, 2016 at 11:00 AM, Yolanda Davis  >
> wrote:
>
> > Resending on appropriate thread:
> >
> > +1 (non-binding)
> >
> > Ran full test suite, with rat and contrib-check.  Verified, readme,
> notice,
> > license, commit ID, hashes and checksums. Tested flows and templates in
> > standalone cluster (on Mac OS).
> >
> > On Fri, Aug 26, 2016 at 12:25 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.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> af92
> > >
> > > 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
> > >
> > > 595 issues were closed/resolved for this release:
> > > 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
> > >
> > > 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
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> >
> >
> >
> > --
> > --
> > yolanda.m.da...@gmail.com
> > @YolandaMDavis
> >
>

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

[Bryan Bende]

+1 (binding) Release this package as nifi-1.0.0

- Verified checksums, signature, commit hash, and LICENSE/NOTICE/README
- Performed full build with contrib-check
- Tested a standalone unsecure instance and then used the toolkit to create
a secure cluster

On Mon, Aug 29, 2016 at 11:00 AM, Yolanda Davis 
wrote:

> Resending on appropriate thread:
>
> +1 (non-binding)
>
> Ran full test suite, with rat and contrib-check.  Verified, readme, notice,
> license, commit ID, hashes and checksums. Tested flows and templates in
> standalone cluster (on Mac OS).
>
> On Fri, Aug 26, 2016 at 12:25 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.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> >
> > Note: There is a second binary being distributed now, the NiFi Toolkit.
> It
> > can be used to facilitate securing a NiFi instance.
> >
> > The Git tag is nifi-1.0.0-RC1
> > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > 1d3c581707
> >
> > Checksums of nifi-1.0.0-source-release.zip:
> > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> >
> > 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
> >
> > 595 issues were closed/resolved for this release:
> > 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
> >
> > 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
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
>
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>

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

[Yolanda Davis]

Resending on appropriate thread:

+1 (non-binding)

Ran full test suite, with rat and contrib-check.  Verified, readme, notice,
license, commit ID, hashes and checksums. Tested flows and templates in
standalone cluster (on Mac OS).

On Fri, Aug 26, 2016 at 12:25 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.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> 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
>
> 595 issues were closed/resolved for this release:
> 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
>
> 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
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
>



-- 
--
yolanda.m.da...@gmail.com
@YolandaMDavis

Re: Apache NiFi 1.0.0 RC1 Release Helper Guide

[Yolanda Davis]

+1 (non-binding)

Ran full test suite, with rat and contrib-check.  Verified, readme, notice,
license, commit ID, hashes and checksums. Tested flows and templates in
standalone cluster (on Mac OS).

On Fri, Aug 26, 2016 at 12:26 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 source release artifacts for review:
>
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.asc
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.md5
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.sha1
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.sha256
>
> # Verify the signature
> gpg --verify nifi-1.0.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-1.0.0-source-release.zip
> sha1sum nifi-1.0.0-source-release.zip
> sha256sum nifi-1.0.0-source-release.zip
>
> # Unzip nifi-1.0.0-source-release.zip
>
> # Verify the build works including release audit tool (RAT) checks
> cd nifi-1.0.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!
>



-- 
--
yolanda.m.da...@gmail.com
@YolandaMDavis

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

[Matt Burgess]

+1 (non-binding)

Verified checksums, GPG signature, commit hash, LICENSE/README/NOTICE,
etc. Tested various flows, templates, controller services on unsecure
standalone and secure 3-node cluster, looking good!

On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
 wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * 
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
> * 
> https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> 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
>
> 595 issues were closed/resolved for this release:
> 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
>
> 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
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!

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

[Joe Skora]

@Pierre, if you don't want it I'd turn off updates, I did NOT get any
special notice until after it had installed.

On Mon, Aug 29, 2016 at 8:09 AM, Pierre Villard  wrote:

> @Joe I don't have the anniversary update yet.
>
> 2016-08-29 13:56 GMT+02:00 Joe Skora :
>
> > To followup, the TestListenSMTP timeout problems got much better when I
> > changed a questionable DNS setting on the router.  They still won't pass
> > within the 5 seconds currently configured in the test, but it was a
> > dramatic change.
> >
> > I was glad to see I wasn't the only one with this problem.
> >
> > Aldrin and Pierre, are you building on Windows 10 before or after the
> > anniversary update?
> >
> > On Mon, Aug 29, 2016 at 4:45 AM, Andy LoPresto <
> alopresto.apa...@gmail.com
> > >
> > wrote:
> >
> > > Pierre and Andre,
> > >
> > > Thanks for reporting the issue where I forgot that some European and
> > > Australian time zones are represented as 4 characters. Obviously the
> test
> > > is overly specific with the regex, as the purpose is to ensure that the
> > > first serialized line is the date and time, and that is still true.
> I'll
> > > take a look at Andre's PR, but it should be an easy fix. Just another
> > > example of i18n biting us. I'll make more of an effort to test with an
> > eye
> > > towards global users from now on.
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > > On Aug 28, 2016, at 22:47, Pierre Villard <
> pierre.villard...@gmail.com
> > >
> > > wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> > > >
> > > > I had the same issue as reported by Joe on SMTP tests with Windows 10
> > > > build. Workaround with timeouts works.
> > > >
> > > > I also reported two minor issues related to timezones (NIFI-2682) /
> > > locale
> > > > (NIFI-2683) aspects.
> > > > NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> > > >
> > > > I ran multiple workflows with a single instance and a three nodes
> > > cluster.
> > > > Checked failover scenario for clustering and exchanges with Kafka
> > > > 0.8/0.9/0.10, with HDFS and with Hive.
> > > >
> > > > Great job!
> > > >
> > > >
> > > > 2016-08-29 7:26 GMT+02:00 Andre :
> > > >
> > > >> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the
> > regex
> > > >> issue.
> > > >>
> > > >>
> > > >>
> > > >>> On Mon, Aug 29, 2016 at 3:07 PM, Andre 
> wrote:
> > > >>>
> > > >>> All,
> > > >>>
> > > >>> Had a look in the groovy code and reason is quite obvious:
> > > >>>
> > > >>> System locale does not match what the code expects via regex.
> > > >>
> > >
> >
>

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

[Pierre Villard]

@Joe I don't have the anniversary update yet.

2016-08-29 13:56 GMT+02:00 Joe Skora :

> To followup, the TestListenSMTP timeout problems got much better when I
> changed a questionable DNS setting on the router.  They still won't pass
> within the 5 seconds currently configured in the test, but it was a
> dramatic change.
>
> I was glad to see I wasn't the only one with this problem.
>
> Aldrin and Pierre, are you building on Windows 10 before or after the
> anniversary update?
>
> On Mon, Aug 29, 2016 at 4:45 AM, Andy LoPresto  >
> wrote:
>
> > Pierre and Andre,
> >
> > Thanks for reporting the issue where I forgot that some European and
> > Australian time zones are represented as 4 characters. Obviously the test
> > is overly specific with the regex, as the purpose is to ensure that the
> > first serialized line is the date and time, and that is still true. I'll
> > take a look at Andre's PR, but it should be an easy fix. Just another
> > example of i18n biting us. I'll make more of an effort to test with an
> eye
> > towards global users from now on.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > > On Aug 28, 2016, at 22:47, Pierre Villard  >
> > wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> > >
> > > I had the same issue as reported by Joe on SMTP tests with Windows 10
> > > build. Workaround with timeouts works.
> > >
> > > I also reported two minor issues related to timezones (NIFI-2682) /
> > locale
> > > (NIFI-2683) aspects.
> > > NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> > >
> > > I ran multiple workflows with a single instance and a three nodes
> > cluster.
> > > Checked failover scenario for clustering and exchanges with Kafka
> > > 0.8/0.9/0.10, with HDFS and with Hive.
> > >
> > > Great job!
> > >
> > >
> > > 2016-08-29 7:26 GMT+02:00 Andre :
> > >
> > >> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the
> regex
> > >> issue.
> > >>
> > >>
> > >>
> > >>> On Mon, Aug 29, 2016 at 3:07 PM, Andre  wrote:
> > >>>
> > >>> All,
> > >>>
> > >>> Had a look in the groovy code and reason is quite obvious:
> > >>>
> > >>> System locale does not match what the code expects via regex.
> > >>
> >
>

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

[Andy LoPresto]

Pierre and Andre,

Thanks for reporting the issue where I forgot that some European and Australian 
time zones are represented as 4 characters. Obviously the test is overly 
specific with the regex, as the purpose is to ensure that the first serialized 
line is the date and time, and that is still true. I'll take a look at Andre's 
PR, but it should be an easy fix. Just another example of i18n biting us. I'll 
make more of an effort to test with an eye towards global users from now on. 

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

> On Aug 28, 2016, at 22:47, Pierre Villard  wrote:
> 
> +1 (non-binding)
> 
> Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> 
> I had the same issue as reported by Joe on SMTP tests with Windows 10
> build. Workaround with timeouts works.
> 
> I also reported two minor issues related to timezones (NIFI-2682) / locale
> (NIFI-2683) aspects.
> NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> 
> I ran multiple workflows with a single instance and a three nodes cluster.
> Checked failover scenario for clustering and exchanges with Kafka
> 0.8/0.9/0.10, with HDFS and with Hive.
> 
> Great job!
> 
> 
> 2016-08-29 7:26 GMT+02:00 Andre :
> 
>> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
>> issue.
>> 
>> 
>> 
>>> On Mon, Aug 29, 2016 at 3:07 PM, Andre  wrote:
>>> 
>>> All,
>>> 
>>> Had a look in the groovy code and reason is quite obvious:
>>> 
>>> System locale does not match what the code expects via regex.
>> 

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

[James Wing]

+1 (non-binding).  I ran through the release helper, including hashes,
build, tests.  No showstopping issues for me.

James

On Fri, Aug 26, 2016 at 9:25 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.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> 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
>
> 595 issues were closed/resolved for this release:
> 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
>
> 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
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
>