Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

[Tony Kurc]

+1 (binding)

- verified hashes and signature
- checked over the README, LICENSE and NOTICE
- build without issue on ubuntu 16.06 (x86_64)
- ran a simple flow without problems

On Mon, May 8, 2017 at 10:57 AM, Kevin Doran 
wrote:

> +1 (non-binding), despite one minor bug found, for which I opened
> MINIFI-303 [1].
>
> - Verified signature, hashes, git commit
> - Built successfully (Mac OS 10.12.4)
> - Verified tests (Mac OS 10.12.4)
> - Verified linting
> - Reviewed README, NOTICE, and LICENSE, both in source and in build output.
> - Verified application works as expected with a few variants of flow
> config file
>
> Potential future improvements (have not created JIRAs or searched for
> existing JIRAs):
>
> - nifi.security.need.ClientAuth property not working when set to false
> (MINIFI-303 opened) [1]
> - Fix or note expected CMake Dev Warning [2]
> - Fix or note expected for compile warnings for civetweb, built under the
> thirdparty/ directory as part of the minifi build. [3]
>
> [1] https://issues.apache.org/jira/browse/MINIFI-303
>
> [2] CMake Warning output:
>
>  CMake Warning (dev) at libminifi/CMakeLists.txt:22 (project):
>   Policy CMP0048 is not set: project() command manages VERSION variables.
>   Run "cmake --help-policy CMP0048" for policy details.  Use the
> cmake_policy
>   command to set the policy and suppress this warning.
>
>   The following variable(s) would be set to empty:
>
> PROJECT_VERSION_MAJOR
> PROJECT_VERSION_MINOR
> PROJECT_VERSION_PATCH
> This warning is for project developers.  Use -Wno-dev to suppress it.
>
>
> [3] Example of civetweb warning:
>
> nifi-minifi-cpp-0.2.0-source/thirdparty/civetweb-1.9.1/src/civetweb.c:14680:56:
> warning: expansion of date or time macro is not reproducible
>   [-Wdate-time]
> NULL, NULL, block, sizeof(block), "Build: %s%s",
> __DATE__, eol);
>
>
>
> On 5/8/17, 10:33, "Bryan Bende"  wrote:
>
> +1 (binding) Release this package as nifi-minifi-cpp-0.2.0
>
> - Verified signature and hashes
> - Built on OSX
> - Successfully ran binary using provided sample config for s2s
>
>
>
> On Mon, May 8, 2017 at 2:26 AM, Koji Kawamura 
> wrote:
> > +1 (non-binding)
> >
> > Full build and test finished successfully without any issue on OS X.
> >
> > Here are the things that I look forward in future improvements
> (didn't
> > check existing JIRAs):
> >
> > 
> --
> > 1. minifi.sh restart does not working?
> > 
> --
> >
> > 'bin/minifi.sh restart' stops existing process, although standard
> > output shows it starts new process, no MiNiFi process is running
> after
> > restart command.
> >
> > $ ./bin/minifi.sh restart
> > Restarting MiNiFi service
> > Stopping MiNiFi (PID: 36353).
> > Starting MiNiFi with PID 36575 and pid file
> > /Users/koji/dev/minifi-0.2.0-vote/nifi-minifi-cpp-0.2.0-
> source/test/nifi-minifi-cpp-0.2.0/bin/.minifi.pid
> >
> > (PID 36575 does not exist after running this command)
> >
> > 
> --
> > 2. How to connect an Output Port to a Processor?
> > 
> --
> >
> > I tried this "Bidirectional Site-To-Site Configuration" example.
> > https://github.com/apache/nifi-minifi-cpp/tree/master/examples/
> BidirectionalSiteToSite
> >
> > Although it's well written and helpful for users to setup
> > bidirectional data transfer between MiNiFi and NiFi, I could not find
> > a way to process data at MiNiFi those are fetched from NiFi.
> >
> > The example describes how to setup remote 'Output Ports' at MiNiFi,
> my
> > MiNiFi seems being able to pull data from NiFi as described in the
> > example.
> > But it doesn't connect the output port to any further processors. I
> > would like to connect it to LogAttribute processor, but couldn't
> > configure the connection properly.
> >
> > It'd be more helpful if the example contains a connection from an
> > Output port to a processor.
> >
> > Thanks,
> > Koji
> >
> >
> > On Mon, May 8, 2017 at 10:49 AM, Joe Witt 
> wrote:
> >> +1 (binding).
> >>
> >> L looks good in source and resulting binary.  Full build and
> >> packaging worked well on OSX.  Resulting binary tested well using
> >> sample config.yml flowing into NiFi.
> >>
> >> Really great progress in the release!
> >>
> >> Couple quick observations; did not file JIRAs or check if existing
> >> ones already there
> >> - s2s logging at info level probably annotates too many flowfile
> >> attribute 

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

[Michael Moser]

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

There was definitely a lot of work that went into this release, many thanks
to all.


On Mon, May 8, 2017 at 2:23 PM, Mark Payne  wrote:

> +1 (binding).
>
> Was able to complete full build w/ contrib check on OSX. Verified
> checksums and that a quick test of functionality
> looks good.
>
>
> > On May 5, 2017, at 10:07 PM, Bryan Bende  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.2.0 (RC2).
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1104
> >
> > The Git tag is nifi-1.2.0-RC2
> > The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 3a605af8e0ac024fb0ba67262d49dab2727b2576
> >
> > Checksums of nifi-1.2.0-source-release.zip:
> > MD5: 90e298a9e23a9dab65358daddd8b5990
> > SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> > SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 381 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12338432
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.2.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test.  The please vote:
> >
> > [ ] +1 Release this package as nifi-1.2.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
>
>

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

[Joseph Niemiec]

+0 (1 Test is failing for me)

* Sig Validated
* Hashes Validated
* Built on Ubuntu 14.04 [Used Ubuntu Package libleveldb1 & cmake 3.2
successfully: Linux edge1 4.4.0-75-generic #96~14.04.1-Ubuntu SMP Thu Apr
20 11:06:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux]
* Running tests I hit a segfault, checking to see if its specific my
environment or not. Working with Mark Parisi to identify root.



Test YAML Config 1
---
/data/ssd01/builds/minifi-020/nifi-minifi-cpp-0.2.0-source/libminifi/test/unit/YamlCongifurationTests.cpp:28
...
/data/ssd01/builds/minifi-020/nifi-minifi-cpp-0.2.0-source/libminifi/test/unit/YamlCongifurationTests.cpp:28:
FAILED:
due to a fatal error condition:
  SIGSEGV - Segmentation violation signal
===
test cases: 15 | 14 passed | 1 failed
assertions: 39 | 38 passed | 1 failed

On Sun, May 7, 2017 at 2:28 PM, Aldrin Piri  wrote:

> Looks like we have removed the problematic areas of the third party
> inclusions, updated the README and updated the tarball generation to avoid
> including generated doc files.  I will being working on an RC2 based off of
> commit hash fa913b4174e1c874ddb12e4901c48bd86a7f70e4.
>
> Thanks!
> Aldrin
>
> On Sat, May 6, 2017 at 10:41 AM, Aldrin Piri  wrote:
>
> > Yep, definitely seems like a good candidate to also include.  Will review
> > that as well and get incorporated if all looks good.  Thanks for bringing
> > to my attention.
> >
> > --aldrin
> >
> > On Sat, May 6, 2017 at 10:35 AM, Marc  wrote:
> >
> >> Aldrin,
> >>   I was preparing a response that we may wish to update the readme per
> >> https://github.com/apache/nifi-minifi-cpp/pull/92 . We don't include
> the
> >> full list of processors. Since the list is small it would be useful to
> >> keep
> >> it up to date at the moment. In the future we can prepare some auto
> >> documentation that we link to from the readme.
> >>
> >>
> >> On Sat, May 6, 2017 at 9:55 AM, Aldrin Piri  wrote:
> >>
> >> > All,
> >> >
> >> > After doing some review for the release process, it was seen that some
> >> > artifacts of our third party dependencies had unknown origins making
> it
> >> > hard to determine the full scope of licensing concerns.  To avoid any
> >> > issues, I am cancelling this vote such that they can be removed.
> >> >
> >> > I have created JIRA issue https://issues.apache.org/jira
> >> /browse/MINIFI-301 to
> >> > track this effort.
> >> >
> >> > Please look for an RC2 later today.
> >> >
> >> > Thanks and apologies,
> >> > Aldrin
> >> >
> >> >
> >> > On May 5, 2017, at 11:40, 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.2.0.
> >> >
> >> > The source archive, signature, and digests can be located at:
> >> >
> >> > Source Archive:
> >> >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz
> >> > GPG armored signature:
> >> >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.asc
> >> > Source MD5:
> >> >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.md5
> >> > Source SHA1:
> >> >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha1
> >> > Source SHA256:
> >> >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha256
> >> >
> >> > The Git tag is minifi-cpp-0.2.0-RC1
> >> > The Git commit hash is b8103f03998820449c24502fa61c224c2e39e098
> >> > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.
> >> > git;a=commit;h=b8103f03998820449c24502fa61c224c2e39e098
> >> > * https://github.com/apache/nifi-minifi-cpp/commit/
> >> > b8103f03998820449c24502fa61c224c2e39e098
> >> >
> >> > Checksums of nifi-minifi-cpp-0.2.0-source.tar.gz:
> >> > MD5: 4aeb83102e95a3d9c3601d1771e67106
> >> > SHA1: f6501f87bde981e31430b13b635bee944d4b3ab3
> >> > SHA256: 8d97eb17c328637058040357523ca99984b4dcfce77d3b5f81128e1f165a
> >> f081
> >> >
> >> > 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
> >> >
> >> > 63 issues were closed/resolved for this release:
> >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > version=12338790=12319921
> >> >
> >> > Release note highlights can be found here:
> >> > https://cwiki.apache.org/confluence/display/MINIFI/
> >> 

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

[Mark Payne]

+1 (binding).

Was able to complete full build w/ contrib check on OSX. Verified checksums and 
that a quick test of functionality
looks good.


> On May 5, 2017, at 10:07 PM, Bryan Bende  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-1.2.0 (RC2).
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1104
> 
> The Git tag is nifi-1.2.0-RC2
> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=3a605af8e0ac024fb0ba67262d49dab2727b2576
> 
> Checksums of nifi-1.2.0-source-release.zip:
> MD5: 90e298a9e23a9dab65358daddd8b5990
> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 381 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338432
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.2.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  The please vote:
> 
> [ ] +1 Release this package as nifi-1.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...

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

[Joe Skora]

+1 binding - release this package as nifi-1.2.0

* confirmed keys, hashes, and commit.
* built with tests and contrib-check on CentOS 7.3.1611, JDK 1.8.0_121, and
Maven 3.3.9.
* checked the README, LICENSE, and NOTICE files.
* ran convenience binary with minimal flow that performed as expected.

Building on Windows 7, with "-DskipTests -Pcontrib-check" I also get errors
for files with bad licenses, but they are all in a ".../target/..."
directory which should be excluded from the check as far as I know.  In
contract, the tests and contrib-check pass on Linux.

On Mon, May 8, 2017 at 1:34 PM, Matt Burgess  wrote:

> +1 (binding) release this package as nifi-1.2.0
>
> Verified hashes & commit, full clean build w/contrib check on OSX El
> Capitan, ran CDC (MySQL to Oracle) flow which exercises the Schema
> Registry and JsonTreeRecordReader as well.
>
> On Fri, May 5, 2017 at 10:07 PM, Bryan Bende  wrote:
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.2.0 (RC2).
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1104
> >
> > The Git tag is nifi-1.2.0-RC2
> > The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 3a605af8e0ac024fb0ba67262d49dab2727b2576
> >
> > Checksums of nifi-1.2.0-source-release.zip:
> > MD5: 90e298a9e23a9dab65358daddd8b5990
> > SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> > SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 381 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12338432
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.2.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test.  The please vote:
> >
> > [ ] +1 Release this package as nifi-1.2.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
>

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

[Matt Burgess]

+1 (binding) release this package as nifi-1.2.0

Verified hashes & commit, full clean build w/contrib check on OSX El
Capitan, ran CDC (MySQL to Oracle) flow which exercises the Schema
Registry and JsonTreeRecordReader as well.

On Fri, May 5, 2017 at 10:07 PM, Bryan Bende  wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-1.2.0 (RC2).
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1104
>
> The Git tag is nifi-1.2.0-RC2
> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=3a605af8e0ac024fb0ba67262d49dab2727b2576
>
> Checksums of nifi-1.2.0-source-release.zip:
> MD5: 90e298a9e23a9dab65358daddd8b5990
> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 381 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338432
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.2.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  The please vote:
>
> [ ] +1 Release this package as nifi-1.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...

Re: Pulling out hair over slf4j...

[Bryan Bende]

Ok thanks for all the info, I am not totally sure what is going, but I
can tell you how the logging JARs are setup in NiFi and maybe that
will shed some light on things...

In the root pom for NiFi there is a dependencyManagement section that
declares slf4j-api, jul-to-slf4j, log4j-over-slf4j, and jcl-over-slf4j
all as provided dependencies to ensure no NARs actually bundle these
since they will be provided directly in the lib directory and
available to all NARs, this also forces them all to
${org.slf4j.version} which in master is 1.7.25:


org.slf4j
jcl-over-slf4j
${org.slf4j.version}
provided


org.slf4j
log4j-over-slf4j
${org.slf4j.version}
provided


org.slf4j
jul-to-slf4j
${org.slf4j.version}
provided


org.slf4j
slf4j-api
${org.slf4j.version}
provided



Then the nifi-assembly pom.xml declares these using compile scope and
puts them in the lib directory:


org.slf4j
jcl-over-slf4j
compile


org.slf4j
jul-to-slf4j
compile


org.slf4j
log4j-over-slf4j
compile


org.slf4j
slf4j-api
compile


Now for Unit tests, the root pom has a regular dependencies section
that has slf4j-simple declared with test scope:


org.slf4j
slf4j-simple
test


So every NAR that is with in the NiFi project will have slf4j-simples
available for unit tests.

Andrew Psaltis also mentions a good point about the different
versions, I believe we just upgraded to 1.7.25 for the 1.2.0 release,
but previous were on 1.7.12, but you should double check that.




On Mon, May 8, 2017 at 12:30 PM, Russell Bateman  wrote:
> Bryan,
>
> Thank you very much for responding. Here's how my project is set up with
> Maven packaging. This is how we've been building our NAR for a year now.
> First, the module list. Except for /nifi-shared/, each module contains NiFi
> custom processors.
>
>nifi-pipeline (root, pom packaging)
>   cda-filter (JAR)
>   fhir-processors (JAR)
>   jdbc (JAR)
>   legacy (JAR)
>   medical-filter (JAR)
>   nifi-shared (JAR)
>   standard-processors (JAR)
>*  imat-pipeline-nar (NAR)*
>
> Here's the /imat-pipeline-nar/'s /pom.xml/ in essence:
>
>   
> com.imatsolutions.nifi.pipeline
> nifi-pipeline
> 1.0.0
> ../pom.xml
>   
>
>   imat-pipeline-nar
>   1.0.0
>   nar
>
>   
> (all those JAR modules)
> 
>   org.apache.nifi
> nifi-dbcp-service-nar
>   ${nifi.version}
>   nar
> 
>   
>
> And here's the project root /pom.xml/ in essence:
>
> com.imatsolutions.nifi.pipeline
>   nifi-pipeline
>   1.0.0
>   pom
>   IMAT Solutions NiFi Pipeline
>   http://imatsolutions.com
>
>   
> nifi-shared
> cda-filter
> fhir-processors
> jdbc
> legacy
> medical-filter
> standard-processors
> imat-pipeline-nar
>   
>
>   
> 
> [1.7.25]
> 1.1.2
> ...
>   
>
>   
> ...
> 
> 
>   org.apache.nifi
>   nifi-api
>   ${nifi.version}
> 
> 
>   org.apache.nifi
>   nifi-utils
>   ${nifi.version}
> 
> 
>   org.apache.nifi
> nifi-processor-utils
>   ${nifi.version}
> 
>
> 
> 
>   org.slf4j
>   slf4j-api
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   slf4j-simple
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   jcl-over-slf4j
>   ${slf4j.version}
> 
> 
>   org.slf4j
> log4j-over-slf4j
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   jul-to-slf4j
>   ${slf4j.version}
> 
> ...
>   
>
>   
> 
>   ...
>   
> 
> org.apache.nifi
> nifi-nar-maven-plugin
> 1.2.0
> true
>   
>   ...
> 
> 
>   
>   
> 
> org.codehaus.mojo
> rpm-maven-plugin
>   2.1.4
>   
> 
>   generate-rpm
>   package
>   
> rpm
>   
> 
>   
>   
> ${psprefix}-${project.artifactId}
> ${psversion}
> ${psrelease}
> Application/System
> 
> perfectsearch-nifi-imat-nar
> 
> Perfect Search Corporation
> Proprietary
> https://software.perfectsearchcorp.com
> A set of NiFi processors for ETL
> 
>   
> /opt/nifi/lib
> false
> 444
> root
> root
> 
>   
> ${project.build.directory}
> 
> *.nar
> 
>   
> 
>   
> 
>   
> 
>   
> 
>   
>
>
> ~/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/ $ mvn
> dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> 
> [INFO] Reactor Build Order:
> 

Re: Pulling out hair over slf4j...

[Andrew Psaltis]

Russell,
In looking at the NiFi 1.1.2 pom [1] it appears that NiFi uses
version 1.7.12 of slf4j, and two of the slf4j dependencies are not marked
with the scope of provided. Specifically, slf4j-log4j12 and slf4j-simple.
That may be causing the issue you are seeing.  Is it possible you can
exclude these slf4j jars from the NiFi dependencies? If I am not mistaken
the syntax should be:


  
   org.apache.nifi
   nifi-api
   ${nifi.version}


  org.slf4j
  slf4j-log4j12


   org.slf4j
   slf4j-simple

  
 
 
   org.apache.nifi
   nifi-utils
   ${nifi.version}


  org.slf4j
  slf4j-log4j12


   org.slf4j
   slf4j-simple

  
 
 
   org.apache.nifi
nifi-processor-utils
   ${nifi.version}


  org.slf4j
  slf4j-log4j12


   org.slf4j
   slf4j-simple

  
 


[1] https://github.com/apache/nifi/blob/rel/nifi-1.1.2/pom.xml

Thanks,
Andrew

On Mon, May 8, 2017 at 12:30 PM, Russell Bateman 
wrote:

> Bryan,
>
> Thank you very much for responding. Here's how my project is set up with
> Maven packaging. This is how we've been building our NAR for a year now.
> First, the module list. Except for /nifi-shared/, each module contains NiFi
> custom processors.
>
>nifi-pipeline (root, pom packaging)
>   cda-filter (JAR)
>   fhir-processors (JAR)
>   jdbc (JAR)
>   legacy (JAR)
>   medical-filter (JAR)
>   nifi-shared (JAR)
>   standard-processors (JAR)
>*  imat-pipeline-nar (NAR)*
>
> Here's the /imat-pipeline-nar/'s /pom.xml/ in essence:
>
>   
> com.imatsolutions.nifi.pipeline
> nifi-pipeline
> 1.0.0
> ../pom.xml
>   
>
>   imat-pipeline-nar
>   1.0.0
>   nar
>
>   
> (all those JAR modules)
> 
>   org.apache.nifi
> nifi-dbcp-service-nar
>   ${nifi.version}
>   nar
> 
>   
>
> And here's the project root /pom.xml/ in essence:
>
> com.imatsolutions.nifi.pipeline
>   nifi-pipeline
>   1.0.0
>   pom
>   IMAT Solutions NiFi Pipeline
>   http://imatsolutions.com
>
>   
> nifi-shared
> cda-filter
> fhir-processors
> jdbc
> legacy
> medical-filter
> standard-processors
> imat-pipeline-nar
>   
>
>   
> 
> [1.7.25]
> 1.1.2
> ...
>   
>
>   
> ...
> 
> 
>   org.apache.nifi
>   nifi-api
>   ${nifi.version}
> 
> 
>   org.apache.nifi
>   nifi-utils
>   ${nifi.version}
> 
> 
>   org.apache.nifi
> nifi-processor-utils
>   ${nifi.version}
> 
>
> 
> 
>   org.slf4j
>   slf4j-api
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   slf4j-simple
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   jcl-over-slf4j
>   ${slf4j.version}
> 
> 
>   org.slf4j
> log4j-over-slf4j
>   ${slf4j.version}
> 
> 
>   org.slf4j
>   jul-to-slf4j
>   ${slf4j.version}
> 
> ...
>   
>
>   
> 
>   ...
>   
> 
> org.apache.nifi
> nifi-nar-maven-plugin
> 1.2.0
> true
>   
>   ...
> 
> 
>   
>   
> 
> org.codehaus.mojo
> rpm-maven-plugin
>   2.1.4
>   
> 
>   generate-rpm
>   package
>   
> rpm
>   
> 
>   
>   
> ${psprefix}-${project.artifactId}
> ${psversion}
> ${psrelease}
> Application/System
> 
> perfectsearch-nifi-imat-nar
> 
> Perfect Search Corporation
> Proprietary
> https://software.perfectsearchcorp.com
> A set of NiFi processors for ETL
> 
>   
> /opt/nifi/lib
> false
> 444
> root
> root
> 
>   
> ${project.build.directory}
> 
> *.nar
> 
>   
> 
>   
> 
>   
> 
>   
> 
>   
>
>
> ~/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/ $ mvn
> dependency:tree
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] IMAT Solutions NiFi Pipeline
> [INFO] nifi-shared
> [INFO] cda-filter
> [INFO] fhir-processors
> [INFO] jdbc
> [INFO] legacy
> [INFO] medical-filter
> [INFO] standard-processors
> [INFO] imat-pipeline-nar
> [INFO]
> [INFO] 
> 
> [INFO] Building IMAT Solutions NiFi Pipeline 1.0.0
> [INFO] 
> 
> [INFO]
> [INFO] --- 

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

[Joey Frazee]

Andy, 

I opened a JIRA [1] and posted a link to the test log output [2]. I’m running 
Docker for Mac 17.03.1-ce-mac5 (16048) and launching the maven:latest container 
with `docker run -it maven:latest /bin/bash`.

Event with a plain clean install (no parallelism or contrib-check) I 
consistently get:

Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.65 sec <<< 
FAILURE! - in org.apache.nifi.provenance.CryptoUtilsTest
testShouldNotValidateUnreadableFileBasedKeyProvider(org.apache.nifi.provenance.CryptoUtilsTest)
  Time elapsed: 0.111 sec  <<< FAILURE!
org.codehaus.groovy.runtime.powerassert.PowerAssertionError: assert 
!unreadableKeyProviderIsValid
   ||
   |true
   false
at 
org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:402)
at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:650)
at 
org.apache.nifi.provenance.CryptoUtilsTest.testShouldNotValidateUnreadableFileBasedKeyProvider(CryptoUtilsTest.groovy:214)

Running org.apache.nifi.provenance.AESProvenanceEventEncryptorTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.285 sec - in 
org.apache.nifi.provenance.AESProvenanceEventEncryptorTest

Results :

Failed tests: 
  CryptoUtilsTest.testShouldNotValidateUnreadableFileBasedKeyProvider:214 
assert !unreadableKeyProviderIsValid
   ||
   |true
   false

1. https://issues.apache.org/jira/browse/NIFI-3836
2. https://gist.github.com/jfrazee/cf097440e0fd882612ba60acb6301134

> On May 8, 2017, at 1:12 AM, Andy LoPresto  wrote:
> 
> Joey,
> 
> I am curious about the test failure. That is the test I refactored due to the 
> POSIX attribute issue failing on Windows right before the RC. It passed when 
> I built on Linux so if you can open a Jira or at least provide me with a 
> stack trace and any steps to make it reproducible, I would appreciate it. 
> 
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> 
>> On May 7, 2017, at 22:17, Joey Frazee  wrote:
>> 
>> +1 (non-binding)
>> 
>> - Verified signature, checksums and commit id
>> - Successfully ran `mvn clean install -Pcontrib-check` on OS X 10.12.4 with 
>> Oracle JDK 1.8.0_121 and Amazon Linux with OpenJDK 1.8.0_121
>> - Successfully ran `mvn clean install -DskipTests` on Docker maven:latest 
>> with OpenJDK 1.8.0_121 but 
>> CryptoUtilsTest.testShouldNotValidateUnreadableFileBasedKeyProvider always 
>> failed with !unreadableKeyProviderIsValid
>> - Built RPM with `mvn -T 4.0C clean install -Prpm,generateArchives 
>> -DskipTests` and tested RPM install
>> - Tested GenerateTableFetch and QueryDatabaseTable with MS SQL 2008 
>> [NIFI-3585], among other flows.
>> 
>>> On May 5, 2017, at 9:07 PM, Bryan Bende  wrote:
>>> 
>>> Hello,
>>> 
>>> I am pleased to be calling this vote for the source release of Apache
>>> NiFi nifi-1.2.0 (RC2).
>>> 
>>> The source zip, including signatures, digests, etc. can be found at:
>>> https://repository.apache.org/content/repositories/orgapachenifi-1104
>>> 
>>> The Git tag is nifi-1.2.0-RC2
>>> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
>>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=3a605af8e0ac024fb0ba67262d49dab2727b2576
>>> 
>>> Checksums of nifi-1.2.0-source-release.zip:
>>> MD5: 90e298a9e23a9dab65358daddd8b5990
>>> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
>>> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
>>> 
>>> Release artifacts are signed with the following key:
>>> https://people.apache.org/keys/committer/bbende.asc
>>> 
>>> KEYS file available here:
>>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>>> 
>>> 381 issues were closed/resolved for this release:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338432
>>> 
>>> Release note highlights can be found here:
>>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.2.0
>>> 
>>> The vote will be open for 72 hours.
>>> Please download the release candidate and evaluate the necessary items
>>> including checking hashes, signatures, build
>>> from source, and test.  The please vote:
>>> 
>>> [ ] +1 Release this package as nifi-1.2.0
>>> [ ] +0 no opinion
>>> [ ] -1 Do not release this package because because...
>> 

Re: Pulling out hair over slf4j...

[Russell Bateman]

Bryan,

Thank you very much for responding. Here's how my project is set up with 
Maven packaging. This is how we've been building our NAR for a year now. 
First, the module list. Except for /nifi-shared/, each module contains 
NiFi custom processors.


   nifi-pipeline (root, pom packaging)
  cda-filter (JAR)
  fhir-processors (JAR)
  jdbc (JAR)
  legacy (JAR)
  medical-filter (JAR)
  nifi-shared (JAR)
  standard-processors (JAR)
   *  imat-pipeline-nar (NAR)*

Here's the /imat-pipeline-nar/'s /pom.xml/ in essence:

  
com.imatsolutions.nifi.pipeline
nifi-pipeline
1.0.0
../pom.xml
  

  imat-pipeline-nar
  1.0.0
  nar

  
(all those JAR modules)

  org.apache.nifi
nifi-dbcp-service-nar
  ${nifi.version}
  nar

  

And here's the project root /pom.xml/ in essence:

com.imatsolutions.nifi.pipeline
  nifi-pipeline
  1.0.0
  pom
  IMAT Solutions NiFi Pipeline
  http://imatsolutions.com

  
nifi-shared
cda-filter
fhir-processors
jdbc
legacy
medical-filter
standard-processors
imat-pipeline-nar
  

  

[1.7.25]
1.1.2
...
  

  
...


  org.apache.nifi
  nifi-api
  ${nifi.version}


  org.apache.nifi
  nifi-utils
  ${nifi.version}


  org.apache.nifi
nifi-processor-utils
  ${nifi.version}





  org.slf4j
  slf4j-api
  ${slf4j.version}


  org.slf4j
  slf4j-simple
  ${slf4j.version}


  org.slf4j
  jcl-over-slf4j
  ${slf4j.version}


  org.slf4j
log4j-over-slf4j
  ${slf4j.version}


  org.slf4j
  jul-to-slf4j
  ${slf4j.version}

...
  

  

  ...
  

org.apache.nifi
nifi-nar-maven-plugin
1.2.0
true
  
  ...


  
  

org.codehaus.mojo
rpm-maven-plugin
  2.1.4
  

  generate-rpm
  package
  
rpm
  

  
  
${psprefix}-${project.artifactId}
${psversion}
${psrelease}
Application/System

perfectsearch-nifi-imat-nar

Perfect Search Corporation
Proprietary
https://software.perfectsearchcorp.com
A set of NiFi processors for ETL

  
/opt/nifi/lib
false
444
root
root

  
${project.build.directory}

*.nar

  

  

  

  

  


~/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/ $ mvn 
dependency:tree

[INFO] Scanning for projects...
[INFO] 


[INFO] Reactor Build Order:
[INFO]
[INFO] IMAT Solutions NiFi Pipeline
[INFO] nifi-shared
[INFO] cda-filter
[INFO] fhir-processors
[INFO] jdbc
[INFO] legacy
[INFO] medical-filter
[INFO] standard-processors
[INFO] imat-pipeline-nar
[INFO]
[INFO] 


[INFO] Building IMAT Solutions NiFi Pipeline 1.0.0
[INFO] 


[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ 
nifi-pipeline ---

[INFO] com.imatsolutions.nifi.pipeline:nifi-pipeline:pom:1.0.0
[INFO] +- com.perfectsearchcorp:medical-filter:jar:195:compile
[INFO] |  +- org.pb:x12:jar:1.0:compile
[INFO] |  +- org.jscience:jscience:jar:4.3.1:compile
[INFO] |  |  \- org.javolution:javolution:jar:5.2.3:compile
[INFO] |  +- ca.uhn.hapi.fhir:hapi-fhir-structures-dstu2:jar:1.5:compile
[INFO] |  |  \- ca.uhn.hapi.fhir:hapi-fhir-base:jar:1.5:compile
[INFO] |  | +- javax.json:javax.json-api:jar:1.0:compile
[INFO] |  | +- org.glassfish:javax.json:jar:1.0.4:compile
[INFO] |  | \- org.codehaus.woodstox:woodstox-core-asl:jar:4.4.1:compile
[INFO] |  |+- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] |  |\- org.codehaus.woodstox:stax2-api:jar:3.1.4:compile
[INFO] |  \- ca.uhn.hapi:hapi-base:jar:2.1:compile
[INFO] +- com.perfectsearchcorp:feeder:jar:195:compile
[INFO] |  +- org.apache.tika:tika-app:jar:1.0:compile
[INFO] |  +- jcifs:jcifs:jar:8:compile
[INFO] |  +- com.sun:yanfs:jar:43:compile
[INFO] |  +- com.sun.mail:javax.mail:jar:1.4.7:compile
[INFO] |  |  \- javax.activation:activation:jar:1.1:compile
[INFO] |  +- commons-codec:commons-codec:jar:1.4:compile
[INFO] |  +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] |  +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] |  +- org.apache.httpcomponents:httpclient:jar:4.1.2:compile
[INFO] |  +- org.apache.httpcomponents:httpclient-cache:jar:4.1.2:compile
[INFO] 

Re: Pulling out hair over slf4j...

[Bryan Bende]

Russell,

Assuming you have the standard project structure with a pom and then
sub-modules for processors and NAR, does your root pom have a parent of
nifi-nar-bundles and if so what version?

Example:


org.apache.nifi
nifi-nar-bundles
1.2.0-SNAPSHOT


It would also be helpful to see the output of mvn dependency:tree
execute from your processors module.

-Bryan


On Mon, May 8, 2017 at 11:33 AM, Russell Bateman 
wrote:

> My nightmare today is a whole test suite of JUnit cases that error out
> with this and it only happens from JUnit tests, never from production code:
>
>
>
> I have put this in my top-level *pom.xml*
>
> [1.7.25]
>
> but that doesn't force-feed the version to NiFi and other dependencies
> that have hard-linked some different version of slf4j? I've tried to
> discover some "common" version of slf4j, but when I wipe it from
> *~/.m2/repository/org/apache/slf4j*, then rebuild, of course I'm left
> still with multiple versions forced upon me:
>
> ~/.m2/repository/org/slf4j $ tree
> .
> ├── jcl-over-slf4j
> │   ├── 1.5.6
> │   ├── 1.7.21
> │   └── 1.7.25
> ├── jul-to-slf4j
> │   └── 1.7.25
> ├── log4j-over-slf4j
> │   └── 1.7.25
> ├── slf4j-api
> │   ├── 1.5.6
> │   ├── 1.6.6
> │   ├── 1.7.10
> │   ├── 1.7.19
> │   ├── 1.7.21
> │   └── 1.7.25
> ├── slf4j-jdk14
> │   └── 1.5.6
> ├── slf4j-parent
> │   ├── 1.5.6
> │   ├── 1.6.6
> │   ├── 1.7.10
> │   ├── 1.7.19
> │   ├── 1.7.21
> │   └── 1.7.25
> └── slf4j-simple
> └── 1.7.25
>
> I've tried mvn dependency:tree commands unsuccessfully to figure out
> which among my dependencies is the culprit. My next lame attempt will be to
> create a fake *slf4j* JAR with the missing method(s), maybe using some
> reflection, etc., but I don't really want to walk that thorny path.
>
> I'm perplexed and don't know how to solve this. I've been just @Ignore-ing
> all these tests for some time now, but I really need them functional. I see
> a lot of folk out there in Googleland with this same question about
> *slf4j*, not always satisfactorily resolve. It's hard to believe that
> others don't have this problem. Incidentally, we don't directly reference
> *slf4j* in our code.
>
> Any thoughts would be helpful. Surely someone brighter than I has
> encountered and solve this problem?
>
>

Re: Issue with NiFi Data Container.

[Gaurav Goyal]

Dear Nifi Experts,

May i request for your review and suggestion?

How can i gracefully stop all nifi processes by executing docker nifi stop.

Regards
Gaurav Goyal

On Fri, May 5, 2017 at 3:56 PM, Gaurav Goyal  wrote:

> I have created nifi docker image.
> When i run into docker nifi, i see following 2 process running
>
> 15-096-Goyal:exanova-templates gaurav.goyal$ docker exec -it
> blissful_banach bash
> bash-4.2$ ps -ef
> UIDPID  PPID  C STIME TTY  TIME CMD
> nifi 1 0  0 19:26 ?00:00:00 /bin/sh bin/nifi.sh run
> nifi17 1  0 19:26 ?00:00:00 /bin/sh bin/nifi.sh run
>
>
> When i run docker nifi stop, it will send kill to PID 1, but it does not
> stop PID 17. Thats why i do not get exitstatus code 0..
> Infact i get code 137.
>
> Does anyone encounter this issue?
>
> May i know the solution please? How can we cleanly stop nifi data
> container.
>
>
> Regards
> Gaurav Goyal
>

Pulling out hair over slf4j...

[Russell Bateman]

My nightmare today is a whole test suite of JUnit cases that error out 
with this and it only happens from JUnit tests, never from production code:




I have put this in my top-level /pom.xml/

   [1.7.25]

but that doesn't force-feed the version to NiFi and other dependencies 
that have hard-linked some different version of slf4j? I've tried to 
discover some "common" version of slf4j, but when I wipe it from 
/~/.m2/repository/org/apache/slf4j/, then rebuild, of course I'm left 
still with multiple versions forced upon me:


   ~/.m2/repository/org/slf4j $ tree
   .
   ├── jcl-over-slf4j
   │   ├── 1.5.6
   │   ├── 1.7.21
   │   └── 1.7.25
   ├── jul-to-slf4j
   │   └── 1.7.25
   ├── log4j-over-slf4j
   │   └── 1.7.25
   ├── slf4j-api
   │   ├── 1.5.6
   │   ├── 1.6.6
   │   ├── 1.7.10
   │   ├── 1.7.19
   │   ├── 1.7.21
   │   └── 1.7.25
   ├── slf4j-jdk14
   │   └── 1.5.6
   ├── slf4j-parent
   │   ├── 1.5.6
   │   ├── 1.6.6
   │   ├── 1.7.10
   │   ├── 1.7.19
   │   ├── 1.7.21
   │   └── 1.7.25
   └── slf4j-simple
└── 1.7.25

I've tried mvn dependency:treecommands unsuccessfully to figure out 
which among my dependencies is the culprit. My next lame attempt will be 
to create a fake /slf4j/ JAR with the missing method(s), maybe using 
some reflection, etc., but I don't really want to walk that thorny path.


I'm perplexed and don't know how to solve this. I've been just 
@Ignore-ing all these tests for some time now, but I really need them 
functional. I see a lot of folk out there in Googleland with this same 
question about /slf4j/, not always satisfactorily resolve. It's hard to 
believe that others don't have this problem. Incidentally, we don't 
directly reference /slf4j/ in our code.


Any thoughts would be helpful. Surely someone brighter than I has 
encountered and solve this problem?

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

[Joseph Niemiec]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

+1

* Verified Hashes
* Verified Signature
* LICENSE and NOTICE appear ok (but its my first time looking at these too)
* Build with - mvn -T 4C -Pcontrib-check clean install and passing
* OS: Ubuntu 14.04, Oracle JDK - jdk1.8.0_77-b03  [Linux edge1
4.4.0-75-generic #96~14.04.1-Ubuntu SMP Thu Apr 20 11:06:30 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux]
* Ran Custom Sample Workflow - ListenUDP + ExecuteScript [Python] +
SplitContent + MergeContent + GZip + RenameFile +  FTP Upload
-BEGIN PGP SIGNATURE-
Version: Keybase OpenPGP v2.0.70
Comment: https://keybase.io/crypto

wsFcBAABCgAGBQJZEILFAAoJEJ+2VIrnunlacakP+wb1b3+I2mTuDMbdfb2E5z6p
RT9LgqMxHyTOGfdgHZrasOjbKdDeqJeb7q07s7cGBa2jo/ILrrEKdthfDUeXpTeA
MuoDaNyMxaFGZHkODeKxdFiZq/Cif4Q3eB2tqFMtx4R2YTmGCsVsbSEoWgVXXvxT
j5NPQx4DARsFyyTuwRH5M0H0gD03VioNRto3p2XlqPn4YdUovOSZQlclSb/fYm2z
7m3SVrK7kBM9WhxIGjJQG4x7QMGDRtQjPy4nPd1c0TuZszvc/LKeboAyRCU8pwXT
a5cIA8/PIKDd0VeiLKtccFJ0dKdWqSjT0yumoGEYrFUnlkhXKH4s2aBmxLRe362D
x043yiA22YYUMcUDb9c8deDKyNlHut9VgzdaNFZSlX4z805DavgRiZ4FeiflGRSH
3FenuBe36p6lR750oGYd4wKiiAhcm8U6cIx2RTSfITamNrlup4itehjFQU2Wod5R
M9nELlvrbsDxblOCdLBJlCH4a+/L3FvaUkxXeMHL3jamjxPj7WAHk0dTu1qrvHcO
OxDu11h8irWuh1GD/C0bWI4Xp2oacTB3Qvv9a4jY4UpPJ5eKE/1YXX45tiBV751x
G58JmtakGQgppil9OX/4XgnlK3AwQWRedddNg50KVcT/i1XKUWM4CeC1uHYQ0UlT
n30vmfIIgQlaBjO5DuFp
=RxKB
-END PGP SIGNATURE-



On Mon, May 8, 2017 at 2:12 AM, Andy LoPresto 
wrote:

> Joey,
>
> I am curious about the test failure. That is the test I refactored due to
> the POSIX attribute issue failing on Windows right before the RC. It passed
> when I built on Linux so if you can open a Jira or at least provide me with
> a stack trace and any steps to make it reproducible, I would appreciate it.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On May 7, 2017, at 22:17, Joey Frazee  wrote:
> >
> > +1 (non-binding)
> >
> > - Verified signature, checksums and commit id
> > - Successfully ran `mvn clean install -Pcontrib-check` on OS X 10.12.4
> with Oracle JDK 1.8.0_121 and Amazon Linux with OpenJDK 1.8.0_121
> > - Successfully ran `mvn clean install -DskipTests` on Docker
> maven:latest with OpenJDK 1.8.0_121 but CryptoUtilsTest.
> testShouldNotValidateUnreadableFileBasedKeyProvider always failed with
> !unreadableKeyProviderIsValid
> > - Built RPM with `mvn -T 4.0C clean install -Prpm,generateArchives
> -DskipTests` and tested RPM install
> > - Tested GenerateTableFetch and QueryDatabaseTable with MS SQL 2008
> [NIFI-3585], among other flows.
> >
> >> On May 5, 2017, at 9:07 PM, Bryan Bende  wrote:
> >>
> >> Hello,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> >> NiFi nifi-1.2.0 (RC2).
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://repository.apache.org/content/repositories/orgapachenifi-1104
> >>
> >> The Git tag is nifi-1.2.0-RC2
> >> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 3a605af8e0ac024fb0ba67262d49dab2727b2576
> >>
> >> Checksums of nifi-1.2.0-source-release.zip:
> >> MD5: 90e298a9e23a9dab65358daddd8b5990
> >> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> >> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912f
> eeb6
> >>
> >> Release artifacts are signed with the following key:
> >> https://people.apache.org/keys/committer/bbende.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>
> >> 381 issues were closed/resolved for this release:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12338432
> >>
> >> Release note highlights can be found here:
> >> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.2.0
> >>
> >> The vote will be open for 72 hours.
> >> Please download the release candidate and evaluate the necessary items
> >> including checking hashes, signatures, build
> >> from source, and test.  The please vote:
> >>
> >> [ ] +1 Release this package as nifi-1.2.0
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because because...
> >
>



-- 
Joseph

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

[Bryan Bende]

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

- Verified signature and hashes
- Built on OSX
- Successfully ran binary using provided sample config for s2s



On Mon, May 8, 2017 at 2:26 AM, Koji Kawamura  wrote:
> +1 (non-binding)
>
> Full build and test finished successfully without any issue on OS X.
>
> Here are the things that I look forward in future improvements (didn't
> check existing JIRAs):
>
> --
> 1. minifi.sh restart does not working?
> --
>
> 'bin/minifi.sh restart' stops existing process, although standard
> output shows it starts new process, no MiNiFi process is running after
> restart command.
>
> $ ./bin/minifi.sh restart
> Restarting MiNiFi service
> Stopping MiNiFi (PID: 36353).
> Starting MiNiFi with PID 36575 and pid file
> /Users/koji/dev/minifi-0.2.0-vote/nifi-minifi-cpp-0.2.0-source/test/nifi-minifi-cpp-0.2.0/bin/.minifi.pid
>
> (PID 36575 does not exist after running this command)
>
> --
> 2. How to connect an Output Port to a Processor?
> --
>
> I tried this "Bidirectional Site-To-Site Configuration" example.
> https://github.com/apache/nifi-minifi-cpp/tree/master/examples/BidirectionalSiteToSite
>
> Although it's well written and helpful for users to setup
> bidirectional data transfer between MiNiFi and NiFi, I could not find
> a way to process data at MiNiFi those are fetched from NiFi.
>
> The example describes how to setup remote 'Output Ports' at MiNiFi, my
> MiNiFi seems being able to pull data from NiFi as described in the
> example.
> But it doesn't connect the output port to any further processors. I
> would like to connect it to LogAttribute processor, but couldn't
> configure the connection properly.
>
> It'd be more helpful if the example contains a connection from an
> Output port to a processor.
>
> Thanks,
> Koji
>
>
> On Mon, May 8, 2017 at 10:49 AM, Joe Witt  wrote:
>> +1 (binding).
>>
>> L looks good in source and resulting binary.  Full build and
>> packaging worked well on OSX.  Resulting binary tested well using
>> sample config.yml flowing into NiFi.
>>
>> Really great progress in the release!
>>
>> Couple quick observations; did not file JIRAs or check if existing
>> ones already there
>> - s2s logging at info level probably annotates too many flowfile
>> attribute details
>> - this warning
>>   '...[minifi log] [error] Site2Site HandShake Failed because
>> destination port is either invalid or full'
>>   might want to rephrase to 'in a stopped state or full'
>> - I believe if these lines appear in the logs
>>   ...[error] NiFi Provenance Repository database open
>> ./provenance_repository fail
>>   ...[error] NiFi FlowFile Repository database open ./flowfile_repository 
>> fail
>>   Then MiNiFi dies on the next usage/movement of data.  This pattern
>> occurred three times.  The exact timing/correlation wasn't clear but
>> this was the only interesting thing I saw in the logs that roughly
>> correlated to the process terminations.
>>
>> Thanks
>> Joe
>>
>> On Sun, May 7, 2017 at 3:53 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.2.0.
>>>
>>> The source archive, signature, and digests can be located at:
>>>
>>> Source Archive:
>>>
>>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz
>>> GPG armored signature:
>>>
>>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.asc
>>> Source MD5:
>>>
>>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.md5
>>> Source SHA1:
>>>
>>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha1
>>> Source SHA256:
>>>
>>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha256
>>>
>>> The Git tag is minifi-cpp-0.2.0-RC2
>>> The Git commit hash is fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>>> *
>>> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>>> *
>>> https://github.com/apache/nifi-minifi-cpp/commit/fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>>>
>>> Checksums of nifi-minifi-cpp-0.2.0-source.tar.gz:
>>> MD5: f9d0f2db0b54ab4b020777669d979e90
>>> SHA1: 05a49e3eb853ec4a35694fd4588df247805a5e3c
>>> SHA256: b88f471292281c5e503d6148c0aa6eb4b4c60d3a6449e924c04ff4761af3ddcb
>>>
>>> Release artifacts are signed with the following key:
>>> https://people.apache.org/keys/committer/aldrin
>>>
>>> KEYS file available here:
>>> 

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

[Andy LoPresto]

Thanks Andre. There is substantial information about the change and some 
discussion with the community on NIFI-3313 [1].

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


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

> On May 8, 2017, at 7:21 AM, Andre  wrote:
> 
> Bryan,
> 
> Thank you for putting this together. Tested on flow with a diverse set of
> processors.
> 
> +1 binding.
> 
> 
> 
> Only notes:
> 
> - I believe the release notes should mention the change of the randomness
> source. While I suspect most will simply ignore, I wouldn't be surprised
> some people will develop some anxiety about the move from /dev/random to
> /dev/urandom
> 
> - Had to rebuild twice due to test failures (provenance tests if I recall
> correctly).
> 
> - I believe this is by design but on a clustered environment, the upgrade
> from 1.2.0-SNAPSHOT to 1.2.0 required cluster bounce (i.e. downtime).
> 
> 
> 
> 
> On Sat, May 6, 2017 at 12:07 PM, Bryan Bende  wrote:
> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache
>> NiFi nifi-1.2.0 (RC2).
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1104
>> 
>> The Git tag is nifi-1.2.0-RC2
>> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>> 3a605af8e0ac024fb0ba67262d49dab2727b2576
>> 
>> Checksums of nifi-1.2.0-source-release.zip:
>> MD5: 90e298a9e23a9dab65358daddd8b5990
>> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
>> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/bbende.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 381 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12316020=12338432
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/
>> Release+Notes#ReleaseNotes-Version1.2.0
>> 
>> The vote will be open for 72 hours.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build
>> from source, and test.  The please vote:
>> 
>> [ ] +1 Release this package as nifi-1.2.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

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

[Andy LoPresto]

If it doesn’t pass on Windows, does it make sense to add a profile trigger to 
avoid running the check entirely if the OS is Windows?

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

> On May 8, 2017, at 7:19 AM, Joe Witt  wrote:
> 
> Yep agreed.  Can do a jira sweep based on vite thread feedback.
> 
> On May 8, 2017 10:14 AM, "Andrew Psaltis"  wrote:
> 
>> Cool -- not sure if it is worth calling that out in next Release Guideline,
>> as it may trip up others or most likely myself again :)
>> 
>> On Mon, May 8, 2017 at 9:54 AM, Joe Witt  wrote:
>> 
>>> Rat check has never worked on windows and is flakey in parallel builds at
>>> best.
>>> 
>>> On May 8, 2017 9:05 AM, "Andrew Psaltis" 
>> wrote:
>>> 
 +0 (non-binding) -- failed building on Windows 10 using mvn clean
>> install
 -Pcontrib-check -DskipTests (skipped test as build with tests failed)
 
 Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
 2017-04-03T15:39:06-04:00)
 Maven home: c:\tools\apache-maven-3.5.0\bin\..
 Java version: 1.8.0_131, vendor: Oracle Corporation
 Java home: C:\Program Files\Java\jdk1.8.0_131\jre
 Default locale: en_US, platform encoding: Cp1252
 OS name: "windows 10", version: "10.0", arch: "amd64", family:
>> "windows"
 
 Build failed  with RAT check against nifi-poi-processors. Not sure if
>>> this
 is expected or not. Details of rat.txt output are:
 
 
 *
 Summary
 ---
 Generated at: 2017-05-08T08:22:12-04:00
 Notes: 0
 Binaries: 2
 Archives: 0
 Standards: 6
 
 Apache Licensed: 5
 Generated Documents: 0
 
 JavaDocs are generated and so license header is optional
 Generated files do not required license headers
 
 1 Unknown Licenses
 
 ***
 
 Unapproved licenses:
 
 
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
 
 ***
 
 Archives:
 
 *
  Files with Apache License headers will be marked AL
  Binary files (which do not require AL headers) will be marked B
  Compressed archives will be marked A
  Notices, licenses etc will be marked N
  AL
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/pom.xml
  AL
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/main/java/org/
 apache/nifi/processors/poi/ConvertExcelToCSVProcessor.java
  AL
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/main/resources/
 META-INF/services/org.apache.nifi.processor.Processor
  AL
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/java/org/
 apache/nifi/processors/poi/ConvertExcelToCSVProcessorTest.java
  B
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/resources/
>> CollegeScorecard.xlsx
  AL
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/resources/logback-test.xml
  B
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/resources/TwoSheets.xlsx
 !?
 C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
 poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
 
 *
 Printing headers for files without AL header...
 
 
 
>> ===
 ==C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/
 nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
 
>> ===
 ÐÏ?ࡱ?á>???þÿ
 ?1???þÿÿÿþÿÿÿ0???
 
 
 
 
 
 
 
>> 
 ???£DÍ?Á???á???°?Á?â???\?pjames
 
 
 B???°?a?À???=?œ???¯?¼?=?
 

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

[Andre]

Bryan,

Thank you for putting this together. Tested on flow with a diverse set of
processors.

+1 binding.



Only notes:

- I believe the release notes should mention the change of the randomness
source. While I suspect most will simply ignore, I wouldn't be surprised
some people will develop some anxiety about the move from /dev/random to
/dev/urandom

- Had to rebuild twice due to test failures (provenance tests if I recall
correctly).

- I believe this is by design but on a clustered environment, the upgrade
from 1.2.0-SNAPSHOT to 1.2.0 required cluster bounce (i.e. downtime).




On Sat, May 6, 2017 at 12:07 PM, Bryan Bende  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-1.2.0 (RC2).
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1104
>
> The Git tag is nifi-1.2.0-RC2
> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 3a605af8e0ac024fb0ba67262d49dab2727b2576
>
> Checksums of nifi-1.2.0-source-release.zip:
> MD5: 90e298a9e23a9dab65358daddd8b5990
> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 381 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12338432
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.2.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  The please vote:
>
> [ ] +1 Release this package as nifi-1.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

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

[Joe Witt]

Yep agreed.  Can do a jira sweep based on vite thread feedback.

On May 8, 2017 10:14 AM, "Andrew Psaltis"  wrote:

> Cool -- not sure if it is worth calling that out in next Release Guideline,
> as it may trip up others or most likely myself again :)
>
> On Mon, May 8, 2017 at 9:54 AM, Joe Witt  wrote:
>
> > Rat check has never worked on windows and is flakey in parallel builds at
> > best.
> >
> > On May 8, 2017 9:05 AM, "Andrew Psaltis" 
> wrote:
> >
> > > +0 (non-binding) -- failed building on Windows 10 using mvn clean
> install
> > > -Pcontrib-check -DskipTests (skipped test as build with tests failed)
> > >
> > > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> > > 2017-04-03T15:39:06-04:00)
> > > Maven home: c:\tools\apache-maven-3.5.0\bin\..
> > > Java version: 1.8.0_131, vendor: Oracle Corporation
> > > Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> > > Default locale: en_US, platform encoding: Cp1252
> > > OS name: "windows 10", version: "10.0", arch: "amd64", family:
> "windows"
> > >
> > > Build failed  with RAT check against nifi-poi-processors. Not sure if
> > this
> > > is expected or not. Details of rat.txt output are:
> > >
> > >
> > > *
> > > Summary
> > > ---
> > > Generated at: 2017-05-08T08:22:12-04:00
> > > Notes: 0
> > > Binaries: 2
> > > Archives: 0
> > > Standards: 6
> > >
> > > Apache Licensed: 5
> > > Generated Documents: 0
> > >
> > > JavaDocs are generated and so license header is optional
> > > Generated files do not required license headers
> > >
> > > 1 Unknown Licenses
> > >
> > > ***
> > >
> > > Unapproved licenses:
> > >
> > >
> > > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> > >
> > > ***
> > >
> > > Archives:
> > >
> > > *
> > >   Files with Apache License headers will be marked AL
> > >   Binary files (which do not require AL headers) will be marked B
> > >   Compressed archives will be marked A
> > >   Notices, licenses etc will be marked N
> > >   AL
> > >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/pom.xml
> > >   AL
> > >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/main/java/org/
> > > apache/nifi/processors/poi/ConvertExcelToCSVProcessor.java
> > >   AL
> > >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/main/resources/
> > > META-INF/services/org.apache.nifi.processor.Processor
> > >   AL
> > >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/java/org/
> > > apache/nifi/processors/poi/ConvertExcelToCSVProcessorTest.java
> > >   B
> > > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/resources/
> CollegeScorecard.xlsx
> > >   AL
> > >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/resources/logback-test.xml
> > >   B
> > > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/resources/TwoSheets.xlsx
> > >  !?
> > > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > > poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> > >
> > > *
> > >  Printing headers for files without AL header...
> > >
> > >
> > > 
> ===
> > > ==C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/
> > > nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> > > 
> ===
> > > ÐÏ?ࡱ?á>???þÿ
> > > ?1???þÿÿÿþÿÿÿ0???
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> 
> > > ???£DÍ?Á???á???°?Á?â???\?pjames
> > >
> > >
> > >  B???°?a?À???=?œ???¯?¼?=?
> > > ??­R“!8???X?@???"???·?Ú?1???
> > > Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?
> > > r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?
> > > a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1?*?h???6?
> > 

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

[Andrew Psaltis]

Cool -- not sure if it is worth calling that out in next Release Guideline,
as it may trip up others or most likely myself again :)

On Mon, May 8, 2017 at 9:54 AM, Joe Witt  wrote:

> Rat check has never worked on windows and is flakey in parallel builds at
> best.
>
> On May 8, 2017 9:05 AM, "Andrew Psaltis"  wrote:
>
> > +0 (non-binding) -- failed building on Windows 10 using mvn clean install
> > -Pcontrib-check -DskipTests (skipped test as build with tests failed)
> >
> > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> > 2017-04-03T15:39:06-04:00)
> > Maven home: c:\tools\apache-maven-3.5.0\bin\..
> > Java version: 1.8.0_131, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> >
> > Build failed  with RAT check against nifi-poi-processors. Not sure if
> this
> > is expected or not. Details of rat.txt output are:
> >
> >
> > *
> > Summary
> > ---
> > Generated at: 2017-05-08T08:22:12-04:00
> > Notes: 0
> > Binaries: 2
> > Archives: 0
> > Standards: 6
> >
> > Apache Licensed: 5
> > Generated Documents: 0
> >
> > JavaDocs are generated and so license header is optional
> > Generated files do not required license headers
> >
> > 1 Unknown Licenses
> >
> > ***
> >
> > Unapproved licenses:
> >
> >
> > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> >
> > ***
> >
> > Archives:
> >
> > *
> >   Files with Apache License headers will be marked AL
> >   Binary files (which do not require AL headers) will be marked B
> >   Compressed archives will be marked A
> >   Notices, licenses etc will be marked N
> >   AL
> >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/pom.xml
> >   AL
> >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/main/java/org/
> > apache/nifi/processors/poi/ConvertExcelToCSVProcessor.java
> >   AL
> >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/main/resources/
> > META-INF/services/org.apache.nifi.processor.Processor
> >   AL
> >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/java/org/
> > apache/nifi/processors/poi/ConvertExcelToCSVProcessorTest.java
> >   B
> > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/resources/CollegeScorecard.xlsx
> >   AL
> >  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/resources/logback-test.xml
> >   B
> > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/resources/TwoSheets.xlsx
> >  !?
> > C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> > poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> >
> > *
> >  Printing headers for files without AL header...
> >
> >
> > ===
> > ==C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/
> > nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> > ===
> > ÐÏ?ࡱ?á>???þÿ
> > ?1???þÿÿÿþÿÿÿ0???
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > ???£DÍ?Á???á???°?Á?â???\?pjames
> >
> >
> >  B???°?a?À???=?œ???¯?¼?=?
> > ??­R“!8???X?@???"???·?Ú?1???
> > Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?
> > r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?
> > a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1?*?h???6?
> > ?C?a?l?i?b?r?i?
> > ?L?i?g?h?t?1???,???6?¼?C?a?l?i?b?r?i?1???6?¼
> > ?C?a?l?i?b?r?i?1???Ü???6?¼?C?a?l?i?b?r?i?1???Ü??
> > ?C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?
> > i?1???Ü??C?a?
> > l?i?b?r?i?1???Ü?¼?C?a?l?i?b?r?i?1???Ü???4?¼?
> > C?a?l?i?b?r?i?1???Ü???4???C?a?l?i?b?r?i?1???Ü???
> > 

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

[Joe Witt]

Rat check has never worked on windows and is flakey in parallel builds at
best.

On May 8, 2017 9:05 AM, "Andrew Psaltis"  wrote:

> +0 (non-binding) -- failed building on Windows 10 using mvn clean install
> -Pcontrib-check -DskipTests (skipped test as build with tests failed)
>
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T15:39:06-04:00)
> Maven home: c:\tools\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Build failed  with RAT check against nifi-poi-processors. Not sure if this
> is expected or not. Details of rat.txt output are:
>
>
> *
> Summary
> ---
> Generated at: 2017-05-08T08:22:12-04:00
> Notes: 0
> Binaries: 2
> Archives: 0
> Standards: 6
>
> Apache Licensed: 5
> Generated Documents: 0
>
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
>
> 1 Unknown Licenses
>
> ***
>
> Unapproved licenses:
>
>
> C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
>
> ***
>
> Archives:
>
> *
>   Files with Apache License headers will be marked AL
>   Binary files (which do not require AL headers) will be marked B
>   Compressed archives will be marked A
>   Notices, licenses etc will be marked N
>   AL
>  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/pom.xml
>   AL
>  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/main/java/org/
> apache/nifi/processors/poi/ConvertExcelToCSVProcessor.java
>   AL
>  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/main/resources/
> META-INF/services/org.apache.nifi.processor.Processor
>   AL
>  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/java/org/
> apache/nifi/processors/poi/ConvertExcelToCSVProcessorTest.java
>   B
> C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/resources/CollegeScorecard.xlsx
>   AL
>  C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/resources/logback-test.xml
>   B
> C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/resources/TwoSheets.xlsx
>  !?
> C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-
> poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
>
> *
>  Printing headers for files without AL header...
>
>
> ===
> ==C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/
> nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
> ===
> ÐÏ?ࡱ?á>???þÿ
> ?1???þÿÿÿþÿÿÿ0???
> 
> 
> 
> 
> 
> 
> 
> ???£DÍ?Á???á???°?Á?â???\?pjames
>
>
>  B???°?a?À???=?œ???¯?¼?=?
> ??­R“!8???X?@???"???·?Ú?1???
> Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?
> r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?
> a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1?*?h???6?
> ?C?a?l?i?b?r?i?
> ?L?i?g?h?t?1???,???6?¼?C?a?l?i?b?r?i?1???6?¼
> ?C?a?l?i?b?r?i?1???Ü???6?¼?C?a?l?i?b?r?i?1???Ü??
> ?C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?
> i?1???Ü??C?a?
> l?i?b?r?i?1???Ü?¼?C?a?l?i?b?r?i?1???Ü???4?¼?
> C?a?l?i?b?r?i?1???Ü???4???C?a?l?i?b?r?i?1???Ü???
> ?¼?C?a?l?i?b?r?i?1???Ü???
> ???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?
> 1???Ü?¼?C?a?l?i?b?r?i?1???Ü???
> ???C?a?l?i?b?r?i??"$"#,##0_);\("$"#,##0\)??!
> ??"$"#,##0_);[Red]\("$"#,##0\)??"??"$"#,##0.00_);\("
> $"#,##0.00\)??'???"??"$"#,##0.00_);[Red]\("$"#,##0.00\)??7?*?2??_("$"*
> #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_)??.?)?)??_(* #,##0_);_(*
> \(#,##0\);_(* 

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

[Andrew Psaltis]

+0 (non-binding) -- failed building on Windows 10 using mvn clean install
-Pcontrib-check -DskipTests (skipped test as build with tests failed)

Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Maven home: c:\tools\apache-maven-3.5.0\bin\..
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_131\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Build failed  with RAT check against nifi-poi-processors. Not sure if this
is expected or not. Details of rat.txt output are:


*
Summary
---
Generated at: 2017-05-08T08:22:12-04:00
Notes: 0
Binaries: 2
Archives: 0
Standards: 6

Apache Licensed: 5
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

1 Unknown Licenses

***

Unapproved licenses:


C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls

***

Archives:

*
  Files with Apache License headers will be marked AL
  Binary files (which do not require AL headers) will be marked B
  Compressed archives will be marked A
  Notices, licenses etc will be marked N
  AL
 
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/pom.xml
  AL
 
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/main/java/org/apache/nifi/processors/poi/ConvertExcelToCSVProcessor.java
  AL
 
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/main/resources/META-INF/services/org.apache.nifi.processor.Processor
  AL
 
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/java/org/apache/nifi/processors/poi/ConvertExcelToCSVProcessorTest.java
  B
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/CollegeScorecard.xlsx
  AL
 
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/logback-test.xml
  B
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/TwoSheets.xlsx
 !?
C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls

*
 Printing headers for files without AL header...


===
==C:/Users/apsal/Downloads/nifi-1.2.0/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls
===
ÐÏ?ࡱ?á>???þÿ
?1???þÿÿÿþÿÿÿ0???
???£DÍ?Á???á???°?Á?â???\?pjames


 
B???°?a?À???=?œ???¯?¼?=???­R“!8???X?@???"???·?Ú?1???Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1?*?h???6?
?C?a?l?i?b?r?i?
?L?i?g?h?t?1???,???6?¼?C?a?l?i?b?r?i?1???6?¼?C?a?l?i?b?r?i?1???Ü???6?¼?C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü??C?a?l?i?b?r?i?1???Ü?¼?C?a?l?i?b?r?i?1???Ü???4?¼?C?a?l?i?b?r?i?1???Ü???4???C?a?l?i?b?r?i?1???Ü???
?¼?C?a?l?i?b?r?i?1???Ü???
???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1???Ü?¼?C?a?l?i?b?r?i?1???Ü???
???C?a?l?i?b?r?i??"$"#,##0_);\("$"#,##0\)??!??"$"#,##0_);[Red]\("$"#,##0\)??"??"$"#,##0.00_);\("$"#,##0.00\)??'???"??"$"#,##0.00_);[Red]\("$"#,##0.00\)??7?*?2??_("$"*
#,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_)??.?)?)??_(* #,##0_);_(*
\(#,##0\);_(* "-"_);_(@_),?:??_("$"* #,##0.00_);_("$"*
\(#,##0.00\);_("$"* "-"??_);_(@_)??6?+?1??_(* #,##0.00_);_(*
\(#,##0.00\);_(* "-"??_);_(@_)à???õÿ ???À à???õÿ
??ôÀ à???õÿ ??ôÀ à???õÿ ??ôÀ à???õÿ
??ôÀ à???õÿ ??ôÀ à???õÿ ??ôÀ à???õÿ
??ôÀ à???õÿ ??ôÀ à???õÿ ??ôÀ à???õÿ
??ôÀ à???õÿ 

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.2.0 (RC2)

[Koji Kawamura]

+1 (non-binding)

Full build and test finished successfully without any issue on OS X.

Here are the things that I look forward in future improvements (didn't
check existing JIRAs):

--
1. minifi.sh restart does not working?
--

'bin/minifi.sh restart' stops existing process, although standard
output shows it starts new process, no MiNiFi process is running after
restart command.

$ ./bin/minifi.sh restart
Restarting MiNiFi service
Stopping MiNiFi (PID: 36353).
Starting MiNiFi with PID 36575 and pid file
/Users/koji/dev/minifi-0.2.0-vote/nifi-minifi-cpp-0.2.0-source/test/nifi-minifi-cpp-0.2.0/bin/.minifi.pid

(PID 36575 does not exist after running this command)

--
2. How to connect an Output Port to a Processor?
--

I tried this "Bidirectional Site-To-Site Configuration" example.
https://github.com/apache/nifi-minifi-cpp/tree/master/examples/BidirectionalSiteToSite

Although it's well written and helpful for users to setup
bidirectional data transfer between MiNiFi and NiFi, I could not find
a way to process data at MiNiFi those are fetched from NiFi.

The example describes how to setup remote 'Output Ports' at MiNiFi, my
MiNiFi seems being able to pull data from NiFi as described in the
example.
But it doesn't connect the output port to any further processors. I
would like to connect it to LogAttribute processor, but couldn't
configure the connection properly.

It'd be more helpful if the example contains a connection from an
Output port to a processor.

Thanks,
Koji


On Mon, May 8, 2017 at 10:49 AM, Joe Witt  wrote:
> +1 (binding).
>
> L looks good in source and resulting binary.  Full build and
> packaging worked well on OSX.  Resulting binary tested well using
> sample config.yml flowing into NiFi.
>
> Really great progress in the release!
>
> Couple quick observations; did not file JIRAs or check if existing
> ones already there
> - s2s logging at info level probably annotates too many flowfile
> attribute details
> - this warning
>   '...[minifi log] [error] Site2Site HandShake Failed because
> destination port is either invalid or full'
>   might want to rephrase to 'in a stopped state or full'
> - I believe if these lines appear in the logs
>   ...[error] NiFi Provenance Repository database open
> ./provenance_repository fail
>   ...[error] NiFi FlowFile Repository database open ./flowfile_repository fail
>   Then MiNiFi dies on the next usage/movement of data.  This pattern
> occurred three times.  The exact timing/correlation wasn't clear but
> this was the only interesting thing I saw in the logs that roughly
> correlated to the process terminations.
>
> Thanks
> Joe
>
> On Sun, May 7, 2017 at 3:53 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.2.0.
>>
>> The source archive, signature, and digests can be located at:
>>
>> Source Archive:
>>
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz
>> GPG armored signature:
>>
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.asc
>> Source MD5:
>>
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.md5
>> Source SHA1:
>>
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha1
>> Source SHA256:
>>
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha256
>>
>> The Git tag is minifi-cpp-0.2.0-RC2
>> The Git commit hash is fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>> *
>> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>> *
>> https://github.com/apache/nifi-minifi-cpp/commit/fa913b4174e1c874ddb12e4901c48bd86a7f70e4
>>
>> Checksums of nifi-minifi-cpp-0.2.0-source.tar.gz:
>> MD5: f9d0f2db0b54ab4b020777669d979e90
>> SHA1: 05a49e3eb853ec4a35694fd4588df247805a5e3c
>> SHA256: b88f471292281c5e503d6148c0aa6eb4b4c60d3a6449e924c04ff4761af3ddcb
>>
>> 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
>>
>> 67 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338790=12319921
>>
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.2.0
>>
>> The vote will be open for 72 hours and will close 10 May at 5PM EDT 

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

[Andy LoPresto]

Joey,

I am curious about the test failure. That is the test I refactored due to the 
POSIX attribute issue failing on Windows right before the RC. It passed when I 
built on Linux so if you can open a Jira or at least provide me with a stack 
trace and any steps to make it reproducible, I would appreciate it. 

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

> On May 7, 2017, at 22:17, Joey Frazee  wrote:
> 
> +1 (non-binding)
> 
> - Verified signature, checksums and commit id
> - Successfully ran `mvn clean install -Pcontrib-check` on OS X 10.12.4 with 
> Oracle JDK 1.8.0_121 and Amazon Linux with OpenJDK 1.8.0_121
> - Successfully ran `mvn clean install -DskipTests` on Docker maven:latest 
> with OpenJDK 1.8.0_121 but 
> CryptoUtilsTest.testShouldNotValidateUnreadableFileBasedKeyProvider always 
> failed with !unreadableKeyProviderIsValid
> - Built RPM with `mvn -T 4.0C clean install -Prpm,generateArchives 
> -DskipTests` and tested RPM install
> - Tested GenerateTableFetch and QueryDatabaseTable with MS SQL 2008 
> [NIFI-3585], among other flows.
> 
>> On May 5, 2017, at 9:07 PM, Bryan Bende  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache
>> NiFi nifi-1.2.0 (RC2).
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1104
>> 
>> The Git tag is nifi-1.2.0-RC2
>> The Git commit ID is 3a605af8e0ac024fb0ba67262d49dab2727b2576
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=3a605af8e0ac024fb0ba67262d49dab2727b2576
>> 
>> Checksums of nifi-1.2.0-source-release.zip:
>> MD5: 90e298a9e23a9dab65358daddd8b5990
>> SHA1: e138941f576bdb1dff17df6674c19ffae3ef6719
>> SHA256: c18398800c435dabff9f45ec55a450ca78c3c1aec222aa295c0e2057912feeb6
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/bbende.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 381 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12338432
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.2.0
>> 
>> The vote will be open for 72 hours.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build
>> from source, and test.  The please vote:
>> 
>> [ ] +1 Release this package as nifi-1.2.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>