Re: State sharing

Andrew, Thanks for the link. My current use case need to store data in centralized key/value store, that can be updated by one Processor and read by couple of different processors in the cluster. Data speed is low (tracking database schema changes) , so concurrently is not big concern. My use c

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

+1 (binding) Ran through the helper and verified functionality of a couple templates. Also successfully built on Windows 8. Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Monday, July 11, 2016 10:31 PM, Matt Gilman wrote: +1 (binding) Matt On S

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

+1 (binding) Matt On Sat, Jul 9, 2016 at 2:47 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache NiFi, > nifi-0.7.0. > > The source zip, including signatures, digests, etc. can be fou

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

+1 (binding) - Verified signatures and hashes - Full build passed with contrib-check - Basic testing of secure and unsecure standalone instance On Mon, Jul 11, 2016 at 8:35 PM, Tony Kurc wrote: > +1 (binding) > > Built and ran some simple test flows on Ubuntu Linux (14.04, x86_64) and > Windows

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

+1 (binding) Built and ran some simple test flows on Ubuntu Linux (14.04, x86_64) and Windows 10 (64 bit) On Mon, Jul 11, 2016 at 4:13 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Dist is updated, the current signature is SHA512. I verified both are > stored on dist as they shoul

Re: External Repositories (aka Extension Registry) for Dynamically-loaded Extensions

Thanks, Joe. I've responded to the issues you raised in Sections 5 and 6. Sections 2 and 3 were written by others and I am reticent to edit their text; I hope they will accept or respond to your comments there. Thanks everyone, --Matt From: Joe Witt Sent

Re: External Repositories (aka Extension Registry) for Dynamically-loaded Extensions

Matt, Puspendu, I put some thoughts on the wiki today and I think it looks like it is coming along nicely. I believe the slow response cycle right now is because there are a few fairly big efforts underway at once including the first release of minifi, apache nifi 0.7.0 voting, and closing down f

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

Dist is updated, the current signature is SHA512. I verified both are stored on dist as they should be: Joseph-Percivall:verify jpercivall$ gpg -v --verify nifi-0.7.0-source-release.zip.asc gpg: armor header: Version: GnuPG v1 gpg: assuming signed data in `nifi-0.7.0-source-release.zip' gpg:

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

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

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

+1 (non-binding), verified artifacts, signatures, etc. Ran various tests with templates, controller services, new processors, etc. On Sat, Jul 9, 2016 at 2:47 PM, Joe Percivall wrote: > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache NiFi, >

Re: External Repositories (aka Extension Registry) for Dynamically-loaded Extensions

Hi all, Looks like this didn't get to the top of anyone's priority list over the holiday week, since the Jira, the Wiki page

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

Totally doable for the artifacts you put up in dist Joe. Basically just replacing the asc file. I'd recommend not worrying about it for the staged maven artifacts. On Mon, Jul 11, 2016 at 2:34 PM, Tony Kurc wrote: > Would it be appropriate to regenerate the signatures? I think Joe Witt may > ha

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

Would it be appropriate to regenerate the signatures? I think Joe Witt may have done something similar recently without cancelling the RC. On Mon, Jul 11, 2016 at 2:05 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > @Tony - I apologize, I did not. I must have accidentally overlooked

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

@Tony - I apologize, I did not. I must have accidentally overlooked that section of the Release Signing page. I just added the proper configuration to my gpg.conf file. Thank you for pointing it out, Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Mon

Re: State sharing

Sumo, Something lightweight I devised here, backed by a simple in mem concurrent map, for cases when a distributed map is too much https://github.com/aperepel/nifi-csv-bundle/tree/master/nifi-csv-processors/src/main/java/org/apache/nifi/processors/lookup In a cluster, though, it's the true distri

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

@JoePercivall - did you go through the steps to avoid SHA1 for signing [1]? When verifying (with verbose) the nifi-0.7.0-source-release.zip.asc, I got this in the output: gpg: binary signature, digest algorithm SHA1 1. http://www.apache.org/dev/openpgp.html#sha1 On Mon, Jul 11, 2016 at 12:50 PM

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

+1 (non-binding) I ran through the release helper and lightly tested the generated binary. On Sat, Jul 9, 2016 at 11:47 AM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache NiFi, > nif