Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

[M Tien]

+1

- Verified checksums, signature,  and commit hash
- LICENSE and NOTICE look good
- Verified npm run clean:install passes
- Verified the demo app works as expected

Thanks!

- Margot

> On Jan 25, 2022, at 2:39 PM, Joe Witt  wrote:
> 
> +1 binding.
> 
> Verified hashes, signature, L, commit.  Ran the build and demo app.
> Checks out fine.
> 
> Please note we should not publish sha1 hashes anymore.  Just delete
> that from the artifacts.
> 
> Thanks for RM efforts!
> 
> Joe
> 
> On Tue, Jan 25, 2022 at 2:41 PM Scott Aslan  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache NiFi
>> Flow Design System nifi-fds-0.3.0.
>> 
>> The source zip, including signatures, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
>> 
>> The Git tag is nifi-0.3.0-RC2
>> The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
>> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
>> 
>> Checksums of nifi-fds-0.3.0-source-release.zip:
>> SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
>> SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
>> SHA512:
>> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/scottyaslan.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 17 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.0
>> 
>> The vote will be open for 72 hours.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.  Then
>> please vote:
>> 
>> [ ] +1 Release this package as nifi-fds-0.3.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...

Re: [ANNOUNCE] New Apache NiFi Committer Margot Tien

[M Tien]

Thanks, everyone! It’s an honor to officially be part of an amazing community.

- Margot

> On Dec 16, 2021, at 6:08 AM, Andrew Lim  wrote:
> 
> Congrats Margot!
> 
>> On Dec 15, 2021, at 4:05 PM, David Handermann  
>> wrote:
>> 
>> Congratulations Margot!
>> 
>> On Wed, Dec 15, 2021 at 2:50 PM Nathan Gough  wrote:
>> 
>>> Congrats Margot, thanks for all your contributions!
>>> 
>>> On Wed, Dec 15, 2021 at 3:02 PM Chris Sampson
>>>  wrote:
>>> 
 Congrat Margot!
 
 ---
 *Chris Sampson*
 IT Consultant
 chris.samp...@naimuri.com
 
 
 On Wed, 15 Dec 2021 at 19:04, Pierre Villard <
>>> pierre.villard...@gmail.com>
 wrote:
 
> Congrats Margot!
> 
> Le mer. 15 déc. 2021 à 20:00, Kevin Doran  a écrit
>>> :
> 
>> Congratulations Margot! Well deserved.
>> 
>>> On Dec 15, 2021, at 13:47, Joe Witt  wrote:
>>> 
>>> Congrats Margot!   And thanks
>>> 
>>> On Wed, Dec 15, 2021 at 11:46 AM Matt Gilman 
>> wrote:
>>> 
 Apache NiFi community,
 
 On behalf of the Apache NiFi PMC, I am very pleased to announce
>>> that
>> Margot
 has accepted the PMC's invitation to become a committer on the
 Apache
>> NiFi
 project. We greatly appreciate all of Margot's hard work and
 generous
 contributions to the project. We look forward to continued
 involvement
>> in
 the project.
 
 Margot has been contributing to NiFi and NiFi Registry for years.
 Her
 contributions have covered both back-end and front-end
>>> improvements
 in
>> both
 projects in addition to release verification and thoughtful PR
> reviews.
 
 Welcome and congratulations!
 
>> 
>> 
> 
 
>>> 
> 

Re: [VOTE] Release Apache NiFi 1.13.1

[M Tien]

+1 (non-binding)

Went through the release helper
Verified a successful build on - 
Zulu OpenJDK 1.8.0_282
Zulu OpenJDK 11.0.10
Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
Set up a secure standalone instance
Set up a secure cluster

Thanks,
Margot Tien


> On Mar 12, 2021, at 12:26 PM, David Handermann  
> wrote:
> 
> +1 non-binding
> 
> Verified release signatures and expected files.
> Verified build on Ubuntu 20.10 using Apache Maven 3.6.3 with Azul Zulu JDK
> 11.0.10.
> Configured and tested InvokeHTTP with multiple configurations including
> disabling HTTP/2.
> 
> Regards,
> David Handermann
> 
> On Fri, Mar 12, 2021 at 2:19 PM Joey Frazee 
> wrote:
> 
>> +1 (non-binding)
>> 
>> - Verified checksums and signatures
>> - Ran full build on Java 1.8 and 11 on Linux
>> - Verified NIFI-3383, NIFI-8231, and NIFI-8200
>> 
>> -joey
>> 
>>> On Mar 12, 2021, at 10:28 AM, Bryan Bende  wrote:
>>> 
>>> +1 (binding)
>>> 
>>> - Verified everything in the standard release helper
>>> - Setup secure standalone instance with SAML authentication
>>> 
 On Fri, Mar 12, 2021 at 10:17 AM Marton Szasz 
>> wrote:
 
 +1 (non-binding)
 
 Followed the release helper guide, tested the binary with a simple flow.
 
 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
 Maven home: /usr/share/maven-bin-3.6
 Java version: 1.8.0_252, vendor: IcedTea, runtime:
>> /opt/icedtea-bin-3.16.0/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: "linux", version: "5.10.12-gentoo-x86_64", arch: "amd64",
 family: "unix"
 
 
> On Fri, 12 Mar 2021 at 13:35, Otto Fowler 
>> wrote:
> 
> +1
> 
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime:
>> /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> 
> 
>> On Mar 11, 2021, at 11:29, Joe Witt  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache
>> NiFi
>> 1.13.1.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1179
>> 
>> The source being voted upon and the convenience binaries can be found
>> at:
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.1/
>> 
>> A helpful reminder on how the release candidate verification process
>> works:
>> 
>> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>> 
>> The Git tag is nifi-1.13.1-RC1
>> The Git commit ID is acbc217cb7002d7489421f4d346b995a43b6ea01
>> 
>> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=acbc217cb7002d7489421f4d346b995a43b6ea01
>> 
>> Checksums of nifi-1.13.1-source-release.zip:
>> SHA256:
>> 0a397df640e579720e26699e38a3738c5be05af01aad8aaeefc04eb58591faac
>> SHA512:
>> 
>> 7f8df759d4345ccd6e75c169bd0aab1b7f4f64bf5a8b11b45bc1d7c8163acd0035922dcdbef232392279f4ea0710d4a97c55d480281bfe1d50b6401295633d48
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/joewitt.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 48 issues were closed/resolved for this release:
>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12348700
>> 
>> Release note highlights can be found here:
>> 
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.1
>> 
>> The vote will be open for 72 hours.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.
>> Then
>> please vote:
>> 
>> [ ] +1 Release this package as nifi-1.13.1
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
> 
>> 

Re: [discuss] we need to enable secure by default...

[M Tien]

Hi,

Agreed that NiFi should be secure by default, or at the very least not 
completely open for direct abuse. 

Although I understand the hesitation of requiring a secure startup can be 
overwhelming for new users or inconvenient for those who just want to “test” 
out NiFi - given the powerful capabilities of NiFi it seems reasonable to 
impose some level of authentication or restriction.

This is where I believe really good documentation of clear, obvious, 
to-the-point instructions to secure NiFi would ease this process. This can 
include written documentation/images/screenshots. I even like Nathan’s 
suggestion of a YouTube/video tutorial for a wider scope of different learning 
preferences. 

Personally, when I encounter something I don’t know how to do in NiFi, the most 
helpful resources have been the short, step-by-step guides online - such as 
Pierre Villard’s blog, Bryan Bende's blog, and Andrew Lim’s walk-through 
videos. Whatever we decide on, whether complicated or not, I think having very 
clear instructions will alleviate barrier issues for all levels of users.

Thanks,
Margot

> On Feb 10, 2021, at 10:14 AM, Joe Witt  wrote:
> 
> Nathan just commented on the Jira about an obvious first step being to
> restrict HTTP to localhost only by default.  This is an easy and
> immediately doable first step.  I am planning to wait for the RC4 creation
> for that PR to land and get merged.
> 
> Thanks
> 
> On Wed, Feb 10, 2021 at 10:24 AM Nathan Gough  wrote:
> 
>> I 100% agree that something needs to be done. We cannot allow NiFi to build
>> a reputation that it is 'insecure' by allowing its default installation to
>> start up without any security. Especially considering how much work we put
>> in to make sure it IS a secure product that integrates with many
>> applications in a secure way. Security reputation is very important for
>> software. If some major exploitation of NiFi were to happen in the future,
>> we should be able to confidently say that we did our absolute best to
>> create a secure application. We shouldn't point at new users and say 'they
>> didn't configure it right'.
>> 
>> Personally, I am in favor of providing automatically generated certificates
>> and requiring the user to insert the client certificate in their browser,
>> and providing instructions and perhaps a YouTube video on how to do that.
>> Yes, X509 certificate errors are confusing and can be difficult for
>> beginners to troubleshoot. But those beginner users will also be the most
>> likely to use NiFi insecurely, connect it to the internet, and become part
>> of a user base who got burnt by NiFi being 'insecure'. I acknowledge this
>> is increasing the barrier for entry. If we intend to use a
>> username/password + server cert for HTTPs but no client cert, as stated
>> above we could automatically generate the password and provide this to the
>> user in a log or file.
>> 
>> 
>> On Wed, Feb 10, 2021 at 12:21 PM David Handermann <
>> exceptionfact...@gmail.com> wrote:
>> 
>>> Integrating an option to use Let's Encrypt would be a great improvement
>>> over self-signed certificates, but it is difficult to support that for
>>> instances of NiFi running on servers without Internet access.  Even when
>>> running NiFi for local development purposes, the development system is
>> not
>>> likely to have a publicly addressable DNS name, so Let's Encrypt is not
>> an
>>> option in those cases.
>>> 
>>> Regards,
>>> David Handermann
>>> 
>>> On Wed, Feb 10, 2021 at 11:09 AM Joe Witt  wrote:
>>> 
 Otto
 
 Installers like you mention are inherently brutal for portability so
>> very
 difficult for us in the community.  From the vendor world we of course
>> do
 things like that.  I think in apache nifi land we need a default 'even
>>> for
 devs' which is not wide open.
 
 James
 
 I do think adding such a warning is good.  But it doesn't help avoid
>>> these
 wildly abusive cases.  We need a secure by default path.  We can
>> probably
 do better than the self signed path if we add a 'before running' step
>> in
 the CLI for the user.  Not sure.
 
 Thanks
 
 On Wed, Feb 10, 2021 at 10:05 AM James Srinivasan <
 james.sriniva...@gmail.com> wrote:
 
> Would a suitably large warning on the http ui be a good starting
>> point?
> 
> Browsers are getting increasingly wary of self signed certs and we
 probably
> don't want to be encouraging people to ignore them.
> 
> What about easier acme+certbot support? (notwithstanding all the non
 public
> deployments)
> 
> On Wed, 10 Feb 2021, 15:25 Otto Fowler, 
>>> wrote:
> 
>> Aren’t most of these applications installed by an installer?
>> Maybe we can have one or more installers that setup a secure
>>> instance,
> and
>> those installers
>> could be the *production* nifi, and keep the zip distribution open
>>> for
>> developers?
>> 
>> 
>>> 

Re: [VOTE] Release Apache NiFi 1.13.0 (rc3)

[M Tien]

+1 (non-binding)

Went through the release helper
Verified a successful build on 
Zulu OpenJDK 1.8.0_282
Zulu OpenJDK 11.0.10
Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
Ran a secure instance with OIDC using Google and Okta
Verified a successful user logout and the JWT is invalidated (NIFI-7584)
Tested with a flow using the CompressContent processor and verified dependent 
properties (NIFI-1121)

Thanks,
Margot

> On Feb 7, 2021, at 8:38 PM, Otto Fowler  wrote:
> 
> +1
> 
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: 
> /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> 
> 
>> On Feb 7, 2021, at 01:09, Joe Witt  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache NiFi
>> 1.13.0.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1177
>> 
>> The source being voted upon and the convenience binaries can be found at:
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.0/
>> 
>> A helpful reminder on how the release candidate verification process works:
>> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>> 
>> The Git tag is nifi-1.13.0-RC3
>> The Git commit ID is 547127c07aa9da2698b8b6f65e990b986065ef18
>> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=547127c07aa9da2698b8b6f65e990b986065ef18
>> 
>> Checksums of nifi-1.13.0-source-release.zip:
>> SHA256: 670f6c97a5a2ea488b3006cd6267fa9f02aeeb0d5d011b02f43f76c51ee787bc
>> SHA512:
>> a9ed5d8b5380bedbb18c94c22ba577901392141ba5f07c0c812e548d88df76a365d99ab7cb890d1803acb2e0f0215c1d6ed9dc4704af1da7e0854ef96fa649ad
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/joewitt.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 253 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12348700
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.0
>> 
>> The vote will be open for 72 hours.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test. Then
>> please vote:
>> 
>> [ ] +1 Release this package as nifi-1.13.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
> 

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

[M Tien]

+1 (non-binding)

Went through the release helper
Verified a successful build on 
Zulu OpenJDK 1.8.0_282
Zulu OpenJDK 11.0.10
Maven 3.6.2
OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
Ran a secure instance with OIDC using Google and Okta
Verified a successful user logout and the JWT is invalidated (NIFI-7584)
Tested with a flow using the CompressContent processor and verified dependent 
properties (NIFI-1121)

Thanks,
Margot

> On Feb 2, 2021, at 6:23 PM, Chad Zobrisky  wrote:
> 
> +1 (non-binding)
> 
> Verified signatures, checksums, README, NOTICE and LICENSE
> 
> Built with maven 3.6.3
> Ubuntu 20.04.1
> openjdk 11.0.9.1 and openjdk 1.8.0_275
> Ran on a secure cluster with java 11.0.9.1 - all previous flows ran as
> expected.
> 
> Thanks,
> Chad
> 
> 
> On Tue, Feb 2, 2021 at 8:15 PM Mark Bean  wrote:
> 
>> +1 (non-binding)
>> 
>> Verified signature and checksums
>> Downloaded source and built with Java 8 and Java 11
>>  mvn -T 1C clean install -Pcontrib-check,include-grpc
>>  MacOS, 10.15.7
>>  Java 11.0.9, x86_64
>>  Java 1.8.0_282, x86_64
>>  Maven 3.6.3
>> Verified README, NOTICE and LICENSE (noting 2020 date in License)
>> Ran in both Java 8 and Java 11 JVM with a _very_ basic flow. All basic
>> functions and UI interaction appear normal.
>> 
>> 
>> 
>> On Tue, Feb 2, 2021 at 7:41 PM Muazma Zahid  wrote:
>> 
>>>  +1 (non-binding)
>>> 
>>> - Ran build with OpenJDK 1.8.0_275 on Linux
>>> - Deployed cluster on Azure and tested standard flows with Blob, ADLS,
>> and
>>> CosmosDB processors.
>>> 
>>> Looks good to me.
>>> 
>>> Thanks
>>> Muazma
>>> 
>>> On Tue, Feb 2, 2021 at 4:35 PM Nathan Gough  wrote:
>>> 
 +1 (non-binding)
 
 - Verified signature and checksums again
 - Ran build with
 java -version
 
 openjdk version "1.8.0_282"
 
 OpenJDK Runtime Environment (Zulu 8.52.0.23-CA-macosx) (build
 1.8.0_282-b08)
 
 OpenJDK 64-Bit Server VM (Zulu 8.52.0.23-CA-macosx) (build 25.282-b08,
 mixed mode)
 
 - Tested secure clusters with TLS ZK, secure Site-to-Site, InvokeHTTP,
 ListenHTTP
 
 On Tue, Feb 2, 2021 at 7:20 PM Joey Frazee >>> .invalid>
 wrote:
 
> +1 (non-binding)
> 
> - Verified checksums, signatures, and commit id
> - Ran builds with Java 1.8 and 11 on Linux and macOS, and validated
>> RPM
> build profile
> - Tested cluster coordination and state management with both embedded
>>> and
> external ZooKeepers with TLS enabled and disabled
> - Verified fix for PutAzureBlobStorage OOME and tested Blob and Queue
> storage with Azurite emulator
> 
> -joey
> 
>> On Feb 2, 2021, at 3:16 PM, Sushil Kumar 
>> wrote:
>> 
>> +1 (non-binding) Release this package as nifi-1.13.0
>> 
>> Deployed this via helm chart(
>> https://github.com/sushilkm/nifi-chart)
 on
>> kubernetes.
>> Thank you to all the contributors and reviewers.
>> 
>> 
>>> On Tue, Feb 2, 2021 at 11:02 AM Matt Burgess <
>> mattyb...@apache.org>
> wrote:
>>> 
>>> +1 (binding) Release this package as nifi-1.13.0
>>> 
>>> Ran through release helper and tried various flows using some of
>> the
>>> new features and capabilities added in 1.13.0.  Thanks for RM'ing
>>> Joe!
>>> 
 On Mon, Feb 1, 2021 at 8:10 PM Joe Witt 
>>> wrote:
 
 Hello,
 
 I am pleased to be calling this vote for the source release of
>>> Apache
>>> NiFi
 1.13.0.
 
 The source zip, including signatures, digests, etc. can be found
>>> at:
 
 https://repository.apache.org/content/repositories/orgapachenifi-1176
 
 The source being voted upon and the convenience binaries can be
>>> found
> at:
 https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.0/
 
 A helpful reminder on how the release candidate verification
>>> process
>>> works:
 
>>> 
> 
 
>>> 
>> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
 
 The Git tag is nifi-1.13.0-RC2
 The Git commit ID is c27e59fc679a2e982102a75b8b8df2b0f062af23
 
>>> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=c27e59fc679a2e982102a75b8b8df2b0f062af23
 
 Checksums of nifi-1.13.0-source-release.zip:
 SHA256:
> 4913dd3d943afac710d1a277bf31beebf7a6207a20e1148849d69511f44fc97b
 SHA512:
 
>>> 
> 
 
>>> 
>> dc9935f0eb8692cd8493f5863bc8ae2ef0b52653fa69ff8b9a7e8db7dbd9ec6561f6ffdca4a1b55e43b289d04f5671f5ab4de30999838c5fca5c282c00a7c7f8
 
 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/joewitt.asc
 
 KEYS file available here:
 https://dist.apache.org/repos/dist/release/nifi/KEYS
 
 238 issues were 

Re: [VOTE] Release Apache NiFi 1.13.0

[M Tien]

+1 non-binding.

Went through the release guide
Verified a full build on JDK 1.8.0_275 and JDK 11.0.5
Verified a secure instance of NiFi
Verified I was able to authenticate with OIDC using Google, Okta, and Azure and 
I can successfully log out and invalidate the JWT.

- Margot

Re: [DISCUSS] Release of Apache NiFi 1.13.0

[M Tien]

Hello,
I am wrapping up NIFI-1355 - Provide dynamic code generated certificates for 
HTTP tests to avoid expiry (https://issues.apache.org/jira/browse/NIFI-1355 
). Planning to open a pull 
request today or tomorrow. If possible, I’d like to get this in to NiFi 1.13.0. 

Thanks,
Margot

> On Jan 12, 2021, at 10:17 AM, Pierre Villard  
> wrote:
> 
> Hi all,
> 
> Current status about what we want to get in based on this thread:
> - NIFI-8034 - PropertyValue.isExpressionLanguagePresent always returns true
> for non-null values - https://github.com/apache/nifi/pull/4746
> - NIFI-7989 - Add Hive "data drift" processor -
> https://github.com/apache/nifi/pull/4750
> - NIFI-7356 - TLS + embedded Zookeeper - pull request to be submitted by
> Nathan
> 
> If we can wrap up these JIRAs, we could get a release candidate for NiFi
> 1.13 soon.
> 
> Thanks,
> Pierre
> 
> 
> 
> Le mer. 6 janv. 2021 à 04:17, Joey Frazee 
> a écrit :
> 
>> I have https://github.com/apache/nifi/pull/4632 which fixes an OOME in
>> PutAzureBlobStorage reported in
>> https://lists.apache.org/x/thread.html/rdef82be24828277b85bdc94dc57a8fb9df6f73552daeda289c941a51%40%3Cusers.nifi.apache.org%3E
>> 
>> It’s a pretty small change.
>> 
>> -joey
>> 
>>> On Jan 5, 2021, at 3:14 PM, Matt Burgess  wrote:
>>> 
>>> I am reviewing a PR at the moment but intend to review the graph stuff
>> right afterwards.
>>> 
 On Jan 5, 2021, at 5:35 PM, Mike Thomsen 
>> wrote:
 
 I have a PR for graph that we need to close out because part of the
>> graph
 bundle will be broken without it.
 
>> On Tue, Jan 5, 2021, 11:50 Mark Bean  wrote:
> 
> I'd like to see this PR completed as well
> https://github.com/apache/nifi/pull/4225
> 
> There's been discussion on it, and I don't see any further objections.
> 
> Thanks,
> Mark
> 
> On Thu, Nov 26, 2020 at 4:55 AM Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
> 
>> Hi community,
>> 
>> Starting a discussion thread around the release of NiFi 1.13.0. We
>> added
>> quite a lot of significant improvements and features since the
>> release of
>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix version. I think it
>> makes
>> sense to consider a new release.
>> 
>> Please share here the JIRAs with opened pull requests that we would
>> need
> to
>> look at to make this release happen.
>> 
>> Thanks,
>> Pierre
>> 
> 
>> 

Re: [VOTE] Release Apache NiFi Registry 0.7.0

[M Tien]

+1 (non-binding)

- Verified checksums, signatures, and commit hash
- Verified README, LICENSE & NOTICE
- Verified full clean build & contrib check on Java 8
- Able to create buckets and versioned flows on non-secure NiFi/Registry

Thanks,
Margot

> On Jul 15, 2020, at 8:31 AM, Bryan Bende  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> Registry 0.7.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1161
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-registry-0.7.0-RC1
> The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac
> 
> Checksums of nifi-registry-0.7.0-source-release.zip:
> SHA256: acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8
> SHA512:
> 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683
> 
> 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
> 
> 19 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12346077
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-registry-0.7.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.11.4

[M Tien]

+1 (non-binding)

- Verified checksums, signatures, and commit hash
- Ran build and all tests on OS X
- Deployed secure standalone instance
- Verified the fix was applied to use keystorePassword when keyPassword is 
empty for nifi.properties, InvokeHTTP, ListenHTTP, and 
HandleHTTPRequest/Response.

Thanks,
M. Tien

> On Mar 18, 2020, at 10:15 AM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.11.4.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1159
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.4/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.11.4-RC1
> The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> 
> Checksums of nifi-1.11.4-source-release.zip:
> SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> SHA512:
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 45 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12347022
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.4
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.11.4
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...