Re: Which version to tag?

2019-02-19 Thread Sivaprasanna
I still don’t see a version tag for 1.10 in Jira board. On Wed, 20 Feb 2019 at 10:04 AM, Joe Witt wrote: > ok now master is at 1.10.0-SNAPSHOT. > > Thanks > > On Tue, Feb 19, 2019 at 10:37 PM Joe Witt wrote: > > > You are free to merge to master on approved/reviewed items as per normal. > >

Re: Which version to tag?

2019-02-19 Thread Joe Witt
ok now master is at 1.10.0-SNAPSHOT. Thanks On Tue, Feb 19, 2019 at 10:37 PM Joe Witt wrote: > You are free to merge to master on approved/reviewed items as per normal. > Current master is on 1.9.0-SNAPSHOT so your edit would need to be as well. > Once the RC completes (which is the case in 14

[RESULT][VOTE] Release Apache NiFi 1.9.0

2019-02-19 Thread Joe Witt
Apache NiFi Community, I am pleased to announce that the 1.9.0 release of Apache NiFi passes with 15 +1 (binding) votes 6 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread:

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

2019-02-19 Thread Andy LoPresto
+1 (binding) Ran through the release guide on Mac OS X 10.14.2. -Verified downloads -Verified GPG signature and SHA-256/SHA-512 checksums -Verified presence of LICENSE, NOTICE, README.md, SECURITY.md -Built with contrib-check and all tests pass -Verified

Re: Which version to tag?

2019-02-19 Thread Joe Witt
You are free to merge to master on approved/reviewed items as per normal. Current master is on 1.9.0-SNAPSHOT so your edit would need to be as well. Once the RC completes (which is the case in 14 minutes at current voting) I'll update the versions on master to 1.10.0-SNAPSHOT and do the signed tag

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

2019-02-19 Thread Jeff
+1 (binding) Release this package as nifi-1.9.0 Ran through the release guide, using Ubuntu 18.10 and jdk 1.8.0_201 Used a flow to test: - PutHDFS fs.permissions.umask-mode usage - Kerberized DBCPConnectionPool - Usage of ExecuteSql (with Kerberized DBCPConnectionPool) and PutHDFS to

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

2019-02-19 Thread Michael Moser
+1 (binding) verified the release using the helper, ran some flows, and ran in a Docker container. -- Mike On Tue, Feb 19, 2019 at 5:10 PM Tony Kurc wrote: > +1 (binding) > > - Went through helper on ubuntu 16.04 (x86) without issue > - ran through some very simple flows > > > On Tue, Feb

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

2019-02-19 Thread Tony Kurc
+1 (binding) - Went through helper on ubuntu 16.04 (x86) without issue - ran through some very simple flows On Tue, Feb 19, 2019 at 5:07 PM Andrew Lim wrote: > +1 (non-binding) > > -Ran full clean install on OS X (10.14.2) > -Ran a flow moving data from MySQL into Kudu (QueryDatabaseTable &

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

2019-02-19 Thread Andrew Lim
+1 (non-binding) -Ran full clean install on OS X (10.14.2) -Ran a flow moving data from MySQL into Kudu (QueryDatabaseTable & updated PutKudu processor) -Reviewed documentation additions/updates Drew > On Feb 16, 2019, at 10:50 PM, Joe Witt wrote: > > Hello, > > I am pleased to be calling

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

2019-02-19 Thread Kevin Doran
+1 (binding) - Verified by following the steps in the release helper. - Created a docker image with the resulting binary and verified Registry integration using apache/nifi-registry:0.3.0 docker container. - Verified bugfix for NIFI-5950 in the rc Everything worked great! Thanks to everyone who

Re: DetectDuplicateRecord Processor

2019-02-19 Thread Adam Fisher
I think your use case would be achieved by specifying one user defined property for the record path to the uuid. If you didn't want the cache between invocations of the processor, you would just set "cache the entry identifier" to false so it would only check for unique values in the file instead

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

2019-02-19 Thread Matt Burgess
+1 (binding) Release this package as nifi-1.9.0 Ran through release helper, tried various flows using several components, everything looks good. Thanks Joe for RM'ing! On Sat, Feb 16, 2019 at 10:50 PM Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of

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

2019-02-19 Thread Matt Gilman
+1 (binding) - Verified signature, checksums, etc - Verified integration with an OIDC Provider Thanks for RMing Joe! Matt On Tue, Feb 19, 2019 at 1:38 PM Bryan Bende wrote: > +1 (binding) > > - Verified everything in the release helper > - Ran a cluster and tested some scenarios for

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

2019-02-19 Thread Bryan Bende
+1 (binding) - Verified everything in the release helper - Ran a cluster and tested some scenarios for auto-loading NARs Minor note - I think it was mentioned already, but the source NOTICE still has the year as 2018. On Tue, Feb 19, 2019 at 12:33 PM Mike Thomsen wrote: > > +1 (binding) > >

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

2019-02-19 Thread Mike Thomsen
+1 (binding) Verified checksums, etc. and ran some simple flows. Didn't find anything broken. On Tue, Feb 19, 2019 at 10:08 AM Mark Payne wrote: > +1 (binding) > > Verified signature > Upgraded cluster that ran 1.9.0-RC1. Started up without issue and has been > running for about 48 hours

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

2019-02-19 Thread Mark Payne
+1 (binding) Verified signature Upgraded cluster that ran 1.9.0-RC1. Started up without issue and has been running for about 48 hours without a problem. All issues raised appear to have been addressed in RC2. Flows consist of Site-to-Site, Load-Balanced Connections, Record-oriented processors,

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

2019-02-19 Thread Otto Fowler
+1 (non-binding) - Verified signature - Verified hashes - Verified the build and tests were successful - Verified Git commit ID - Binary starts as expected On February 16, 2019 at 22:50:46, Joe Witt (joew...@apache.org) wrote: +1 (non-binding) - Verified signature - Verified hashes - Verified

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

2019-02-19 Thread James Wing
+1 (binding) - Ran through the release helper, full build and test flow with the resulting binary. Thanks for putting this together, Joe. On Sat, Feb 16, 2019 at 7:50 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.9.0. > >

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

2019-02-19 Thread Marc Parisi
+1 ( binding ) verified sigs and hashes. Built and tested with centos and u18, performing simple flow verification with minifi and registry. On Tue, Feb 19, 2019 at 9:09 AM Aldrin Piri wrote: > +1, binding > > signature good > hashes looked good > full build and tests looked good on macos

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

2019-02-19 Thread Aldrin Piri
+1, binding signature good hashes looked good full build and tests looked good on macos 10.14 and Debian 9 performed some simple flows pulling from registry verified site to site functionality On Tue, Feb 19, 2019 at 8:24 AM Laszlo Horvath wrote: > +1 (non-binding) > > - Verified signature > -

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

2019-02-19 Thread Laszlo Horvath
+1 (non-binding) - Verified signature - Verified hashes - Verified the build and tests were successful - Verified Git commit ID - Binary starts as expected Regards, Laszlo On 19/02/2019, 10:17, "Koji Kawamura" wrote: +1 Release this package as nifi-1.9.0 (binding) - Verified

Re: DetectDuplicateRecord Processor

2019-02-19 Thread Mike Thomsen
I'll have to look at Adam's code in more depth, but I think one reason we might need two is that I didn't see any ability to just check an existing record path against the cache and call it a day. For teams using a standard UUID scheme, that's all we'd need or want. Could be wrong abut that and

Re: DetectDuplicateRecord Processor

2019-02-19 Thread Joe Witt
Mike, Adam, It appears the distinction of interest here between the two general approaches is less about in-mem vs map cache and instead is more about approximate/fast detection vs certain/depending on size of cache approaches. I'm not sure if this is quite right or if the distinction warrants

Re: Which version to tag?

2019-02-19 Thread Mike Thomsen
Probably best to just hold off until the RC2 voting is done because you might have to update it twice if it gets tagged 1.10 and 1.9RC2 fails. On Tue, Feb 19, 2019 at 6:08 AM Sivaprasanna wrote: > All, > > I have just now merged PR 3285 to master. The associated Jira is NIFI-5987 >

Which version to tag?

2019-02-19 Thread Sivaprasanna
All, I have just now merged PR 3285 to master. The associated Jira is NIFI-5987 . Now, since Apache NiFi 1.9.0 rc-2 is in voting, I'm confused whether to tag this particular issue with 1.9.0 version or not. I don't see the version tag for the next

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

2019-02-19 Thread Koji Kawamura
+1 Release this package as nifi-1.9.0 (binding) - Verified signature and hashes - Clean build & test passed - Tested flows using standalone and secure cluster environments Thanks, Koji On Mon, Feb 18, 2019 at 10:30 PM Denes Arvay wrote: > > +1 Release this package as nifi-1.9.0 (non-binding) >