-1 (binding)

Was able to download and build the artifacts. Started NiFi and verified the new 
secure-by-default features. Created a cluster that used certificates. All of 
these worked well.

Started NiFi Registry and created a bucket. Verified that my cluster and 
standalone nodes both were able to interact with the registry properly, pushing 
to, pulling from, and changing versions.

I then built a flow and tried to run it in Stateless NiFi, but when I attempted 
to startup stateless, I found that Stateless always encounters 
NullPointerException on startup. This appears to be due to a very recent commit.

2021-07-09 19:40:27,959 INFO [main] o.a.n.s.f.StandardStatelessDataflowFactory 
Setting java.security.krb5.conf to /etc/krb5.conf
Exception in thread "main" java.lang.NullPointerException
        at 
org.apache.nifi.groups.StandardProcessGroup.<init>(StandardProcessGroup.java:282)
        at 
org.apache.nifi.groups.StandardProcessGroup.<init>(StandardProcessGroup.java:247)
        at 
org.apache.nifi.stateless.engine.StatelessFlowManager.createProcessGroup(StatelessFlowManager.java:217)
        at 
org.apache.nifi.stateless.flow.StandardStatelessDataflowFactory.createDataflow(StandardStatelessDataflowFactory.java:219)
        at 
org.apache.nifi.stateless.bootstrap.StatelessBootstrap.createDataflow(StatelessBootstrap.java:66)
        at 
org.apache.nifi.stateless.bootstrap.RunStatelessFlow.createDataflow(RunStatelessFlow.java:94)
        at 
org.apache.nifi.stateless.bootstrap.RunStatelessFlow.main(RunStatelessFlow.java:56)

> On Jul 9, 2021, at 5:14 PM, Joe Witt <[email protected]> wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.14.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1182
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.14.0/
> 
> Please note that this release now includes the convenience binaries for
> Apache NiFi, NiFi toolkit, MiNiFi, MiNiFi Toolkit, Registry, Registry Toolkit,
> and Stateless NiFi.
> 
> Due to a mistake in the process of creating RC1 the hashes for the
> artifacts published
> to the Nexus repository will not match those of the generated
> convenience binaries.
> While desirable this is not strictly necessary.  I'll try to follow
> the more ideal steps
> if we end up with an RC2.
> 
> Given this vote is going up late on a Friday and this is a very
> significant release I expect to leave the vote up for more than 72
> hours.
> 
> 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.14.0-RC1
> The Git commit ID is 9721a534a943bd9c4720687f165227225e902dad
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=9721a534a943bd9c4720687f165227225e902dad
> 
> Checksums of nifi-1.14.0-source-release.zip:
> SHA256: a6afc174e64c3f56d3945892b1e85d5bf90c6d7626ba9e9b63e43d2168b6fffc
> SHA512: 
> 33d7bc6bc756f4024a390dd0b8a4fed1f18386bc29e86537c59ab99ce6580b4b9e9f48a309f5af90fe5e766afd796f22b3407a130423920a918776819f3d8997
> 
> 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
> 
> 326 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12349644
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.14.0
> 
> The vote will be open for at least 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.14.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Reply via email to