Team,
Here again is guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/release/nifi/KEYS
# Import keys file:
gpg --import KEYS
# [optional] Clear out local maven artifact repository
# Pull
I've verified the signature, hashes, built on Ubuntu 14.04 (x86_64) with
Oracle java 7. Built binaries worked as expected.
Licence and notice look good
+1
+1 (binding)
Went through the RC validation procedure. All looks good. Ran on a
single node + cluster + SSL + LDAP and went through pretty
Hello NiFi Community,
I am pleased to be calling this vote for the source release of Apache
NiFi 0.4.1.
The source zip, including signatures, digests, and associated
convenience binaries can be found at
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.1/
The staged maven artifacts of the
+1 (binding)
Went through the RC validation procedure. All looks good. Ran on a
single node + cluster + SSL + LDAP and went through pretty much all of
the bugs and verified behavior.
Thanks
Joe
On Sat, Dec 19, 2015 at 12:59 PM, Matt Gilman wrote:
> [X] +1 Release
Just a heads up for anyone playing along at home. The GitHub mirror seems
to be lagging behind our core, ASF repository and the associated tag with
the specified commit is not currently mirrored. When verifying source if
you default to GitHub and are unable to checkout that revision, please try
[X] +1 Release this package as Apache NiFi 0.4.1 (binding)
On Sat, Dec 19, 2015 at 10:45 AM, Joe Witt wrote:
> Hello NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 0.4.1.
>
> The source zip, including signatures, digests, and
I agree, I think we discussed it before and the Kafka upgrade doesn't belong in
41
Sent from my iPhone
> On Dec 18, 2015, at 23:26, Sean Busbey wrote:
>
> with the Kafka client change backed out for 0.5.0, I'm good to go with
> 0.4.1 on the rest of the changes.
>
>> On
Hi,
I’m working in a team and we’re hoping to be able to configuration manage flow
templates, but the fact that the export is non-deterministic makes comparisons
very hard.
The jira issue NIFI-826 covers this problem and there was some work done in the
area in August but then it went quiet.
Richard,
As I recall there was a pretty significant effort on this but a couple
roadblocks were hit. With the template/registry and CM feature
proposals we have outstanding the intent is to provide a much richer
user experience around template configuration management and sharing.
That said, it