Re: [discuss] nifi 2.0 and Java 17...
The major issue for our deployments would be the removal of Nashorn as well. Would GraalVM or an alternative be considered as a part of an initial NiFi 2.0 release? Thanks, Ryan On Mon, Jun 5, 2023 at 12:38 PM Joe Witt wrote: > Team, > > Looking like we will update the NiFi 2.0 goals to be based on Java 17 > instead of 11. > > The noted concern around Java removing Nashorn in 11/17 we will need to > identify an alternative plan for regardless and seems like David's proposal > would do the trick. > > Let's give this thread a few more days and if still seems consensus is > present lets just assume lazy consensus and update the NiFi 2.0 goals and > make it happen. > > Thanks > > On Fri, Jun 2, 2023 at 8:46 AM David Handermann < > exceptionfact...@apache.org> > wrote: > > > I agree that moving forward with Java 17 as the minimum for NiFi 2.0 is > the > > best approach given the extended lifecycle of support for Java 17. > > > > With the removal of a number of legacy components, the current main > branch > > is in a much better position to make Java 17 the minimum. > > > > The deprecation and removal of Nashorn from the JDK is worth > highlighting, > > but it should not be a blocker for moving to Java 17. In this case, NiFi > is > > reflecting the deprecation of Nashorn that already exists in Java 11. I > > have submitted a PR for NIFI-11630 to mark ECMAScript as deprecated for > the > > support branch in subsequent version 1 releases. > > > > With that background, there is ongoing maintenance of the Nashorn engine > as > > an external library, in addition to the GraalVM solution. However, this > is > > a good opportunity to take a different approach to scripting engine > > integration. For maintenance and security purposes, it would be much > better > > to reduce the number of bundled scripting engines and make it easier to > > bring your own. The current scripting bundle is around 100 MB, which is a > > lot of weight for languages and solutions that do not apply across the > > board. Providing an alternative that makes it easier to bring in a script > > engine library should provide a better solution for the future. This also > > should not be a blocker for an initial NiFi 2.0, but it is worth > > highlighting given the general interest in scripted components. > > > > Regards, > > David Handermann > > > > On Thu, Jun 1, 2023, 11:38 PM Dirk Arends > > wrote: > > > > > Hi Joe, > > > > > > > Who will be seriously impacted by the removal of Java 11 and what was > > > your plan for upgrading to Java 17? > > > > > > > > > > > > > > thoughts? > > > > > > I would support moving the minimum Java version to 17 if it wasn’t for > > the > > > fact that Nashorn will be removed. Nashorn is already deprecated in > Java > > > 11, and was then fully removed in Java 15. I understand GraalVM is > > intended > > > to be its successor, however this has not yet been integrated into NiFi > > and > > > I’ve been unable to satisfactorily integrate it myself to date. > > > > > > In my NiFi usage, I make heavy use of the JavaScript engine in > > > ExecuteScript and InvokeScriptedProcessor processors. To take advantage > > of > > > GraalVM supporting later ECMAScript versions than Nashorn, I have been > > > attempting to use GraalVM as the JavaScript Engine for NiFi with > limited > > > success. > > > > > > Further details have been provided in JIRA ticket NIFI-6229 [1] and I’d > > > welcome any assistance in trying to finalise GraalVM support, but > > otherwise > > > I’d consider the loss of Nashorn to be a potential blocker to adopting > > Java > > > 17. > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-6229 > > > > > > > > > Regards, > > > > > > Dirk Arends > > > > > > > > > > > > On Thu, 1 Jun 2023 at 03:23, Joe Witt wrote: > > > > > > > Team, > > > > > > > > We've discussed in the past having NiFi 2.0 move from Java 8 to Java > 11 > > > as > > > > the required minimum while also working on Java 17. > > > > > > > > As we move on in time though we are now 4 months (Sept) from. Java 11 > > > > openJDK going end of support. Meanwhile, the Spring 5.x line goes > end > > of > > > > support as of next year and Spring 6.x requires Java 17. Also Java > 21 > > > > comes out in Sept as well and is already the next LTS release. > > > > > > > > I am increasingly of the view that we should seriously > discuss/consider > > > > moving to Java 17 as our basis for NiFi 2.0 as otherwise it basically > > > means > > > > we'll be forced to move to NiFi 3.0 quite quickly. > > > > > > > > We already know we can build and run on Java 17 so we're good there. > > > We'll > > > > soon want to do the same for Java 21 ... and the more 'old stuff' we > > hold > > > > on to the harder it is. > > > > > > > > Who will be seriously impacted by the removal of Java 11 and what was > > > your > > > > plan for upgrading to Java 17? > > > > > > > > thoughts? > > > > > > > > Thanks > > > > > > > > > > > > > -- > > > Regards, > > > > > > -- > > > Dirk
Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)
+1 (non-binding) Downloaded source and performed checksum validation Built with empty maven repo on Ubuntu 22.04.2, maven version 3.6.3 Repeated build with unit tests using the following versions of Java - openjdk version "1.8.0_362" - openjdk version "11.0.19" 2023-04-18 - openjdk version "17.0.7" 2023-04-18 Migrated NiFi Registry from 1.19.1 to 1.22.0 - No issues; all versioned flows from Registry 1.19.1 visible in 1.22.0 Migrated flow from NiFi 1.19.1 to 1.22.0 - No issues; NiFi started successfully and flow was fully operational. Flow consisted of only a dozen or so processors. - Successfully instantiated new versioned flows from NiFi Registry 1.22.0 - Clustering not tested There was a quirk with the UI when adding the 1.22.0 Registry client, but nothing worth holding up the release. Will investigate further and file a Jira issue if repeatable. On Tue, Jun 6, 2023 at 5:38 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.22.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1228 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1 > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > Checksums of nifi-1.22.0-source-release.zip: > SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743 > SHA512: > > 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5 > > 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 > > 186 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353069 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Re: Possible Docker bug in 1.13.2
The DockerImage.txt file isn't always updated in the repo, a bit like the README for Docker Hub - it probably should be, but is often forgotten (same for all of the convenience images built after a release). Indeed, this is currently set to 1.15.1 on `main`, but the images in Docker Hub since then have certainly not used an incorrect version. Nifi 1.16.0 [1] updated the DockerBuild.sh script to allow easier specification of the NIFI_IMAGE_VERSION from the command line. A small issue has just been spotted with this script's use of the text file to obtain the version's default value too [4]. Before then, I think the process was for someone (with access to push images to Docker Hub) to change the text file locally, build & push the image, but not always then raise a PR to update the text file. To manually build the Docker Image locally containing the correct version of the downloaded convenience binary from the Apache servers, simply recreate the `docker build` command from within the DockerBuild.sh [2] file, substituting the correct values for the `--build-arg`s. Alternatively, run the dockermaven [3] build for the repo (having checked out the correct tag from GitHub), enabling the `-P docker` profile as you do so in your `mvn` command. Note, however, that there were differences between the dockermaven and dockerhub builds (both the included script files and the Dockerfile structure) that weren't rationalised until NiFi 1.16.0+. [1]: https://github.com/apache/nifi/blob/rel/nifi-1.16.0/nifi-docker/dockerhub/DockerBuild.sh [2]: https://github.com/apache/nifi/blob/rel/nifi-1.13.2/nifi-docker/dockerhub/DockerBuild.sh#L36 [3]: https://github.com/apache/nifi/tree/rel/nifi-1.16.0/nifi-docker/dockermaven [4]: https://apachenifi.slack.com/archives/CDGMCSDJT/p1686135561932289?thread_ts=1686135561.932289=CDGMCSDJT On Thu, 8 Jun 2023, 00:10 Russell Bateman, wrote: > I'm re-rolling in order to update the Java inside to 11 in order to > permit using the new Java HTTP client. This seems to work well; I fixed > the bug locally. > > Maybe too old to be important, but NiFi 1.14.0 is a quantum step up for > several aspects of processor writing requiring refactoring. So, until we > can shed the old NAR we cannot rebuild, we're stuck at NiFi 1.13.2. > > > On 6/7/23 15:31, Russell Bateman wrote: > > I downloaded sources to 1.13.2 in order to hand-spin my own container > > image. When I got down to > > /nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found: > > > > ... > > ARG NIFI_VERSION=1.13.1 > > ... > > > > and the version is also wrong in /DockerImage.txt/ which > > /DockerBuild.sh/ consumes. > > > > Indeed, the image that is built appears to be versioned 1.13.1 and not > > 1.13.2 when listing local Docker repository images: > > > > *REPOSITORY TAG IMAGE ID CREATED SIZE* > > apache/nifi 1.13.1 8c18038f152a 30 minutes ago 2.06GB > > > > Why am I juggling so ancient a version? Because I have custom > > processors that cannot be rebuilt (source-code gone) and will not run > > on 1.14.0 and later. > > > > Russ >
Re: Possible Docker bug in 1.13.2
I'm re-rolling in order to update the Java inside to 11 in order to permit using the new Java HTTP client. This seems to work well; I fixed the bug locally. Maybe too old to be important, but NiFi 1.14.0 is a quantum step up for several aspects of processor writing requiring refactoring. So, until we can shed the old NAR we cannot rebuild, we're stuck at NiFi 1.13.2. On 6/7/23 15:31, Russell Bateman wrote: I downloaded sources to 1.13.2 in order to hand-spin my own container image. When I got down to /nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found: ... ARG NIFI_VERSION=1.13.1 ... and the version is also wrong in /DockerImage.txt/ which /DockerBuild.sh/ consumes. Indeed, the image that is built appears to be versioned 1.13.1 and not 1.13.2 when listing local Docker repository images: *REPOSITORY TAG IMAGE ID CREATED SIZE* apache/nifi 1.13.1 8c18038f152a 30 minutes ago 2.06GB Why am I juggling so ancient a version? Because I have custom processors that cannot be rebuilt (source-code gone) and will not run on 1.14.0 and later. Russ
Re: Possible Docker bug in 1.13.2
> Because I have custom processors that cannot be rebuilt (source-code gone) IntelliJ can probably give you a close version of the source code if you expand the JAR and drag the class files for your custom code into the IDE. On Wed, Jun 7, 2023 at 5:32 PM Russell Bateman wrote: > I downloaded sources to 1.13.2 in order to hand-spin my own container > image. When I got down to > /nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found: > > ... > ARG NIFI_VERSION=1.13.1 > ... > > and the version is also wrong in /DockerImage.txt/ which > /DockerBuild.sh/ consumes. > > Indeed, the image that is built appears to be versioned 1.13.1 and not > 1.13.2 when listing local Docker repository images: > > *REPOSITORY TAG IMAGE ID CREATED SIZE* > apache/nifi 1.13.1 8c18038f152a 30 minutes ago 2.06GB > > Why am I juggling so ancient a version? Because I have custom processors > that cannot be rebuilt (source-code gone) and will not run on 1.14.0 and > later. > > Russ
Possible Docker bug in 1.13.2
I downloaded sources to 1.13.2 in order to hand-spin my own container image. When I got down to /nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found: ... ARG NIFI_VERSION=1.13.1 ... and the version is also wrong in /DockerImage.txt/ which /DockerBuild.sh/ consumes. Indeed, the image that is built appears to be versioned 1.13.1 and not 1.13.2 when listing local Docker repository images: *REPOSITORY TAG IMAGE ID CREATED SIZE* apache/nifi 1.13.1 8c18038f152a 30 minutes ago 2.06GB Why am I juggling so ancient a version? Because I have custom processors that cannot be rebuilt (source-code gone) and will not run on 1.14.0 and later. Russ
Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)
+1 non binding Verified source release checksums Built w/ java version 17 *Apache Maven 3.9.2* Checks completed NiFi 1.22 started and imported test flow to verify NIFI-11608 as expected Thanks Joe!! On Wed, Jun 7, 2023 at 9:07 AM Mathew Kiprop wrote: > Hello, > > +1 non-binding > > Run through the verification process. Everything checks out well. > Built NiFi with java version 1.8.0_362-8u372-ga~us1-0ubuntu1~22.04-b09 > and apache-maven-3.9.2. > Started NiFi and created basic flows. > Verified > - DBCP Verification Error - Fails to configure data source[1] > - Bulletin causes UI to think it cannot refresh [2] > - Expose JMX metrics from NiFi JVM [3] > > Tested new ModifyCompression Processor[4]. (My concern on this is that when > you specify an incompatible input compression strategy, the processing > fails with no useful message for the user to do the needful). It does not > seem to be a blocker to me for the release. > > Thanks Joe for RM'ing. > > > [1] https://issues.apache.org/jira/browse/NIFI-11547 > [2] https://issues.apache.org/jira/browse/NIFI-11560 > [3] https://issues.apache.org/jira/browse/NIFI-11385 > [4] https://issues.apache.org/jira/browse/NIFI-11466 > > On Wed, Jun 7, 2023 at 12:38 AM Joe Witt wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.22.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1228 > > > > The source being voted upon and the convenience binaries can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1 > > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > > > > https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > > > Checksums of nifi-1.22.0-source-release.zip: > > SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743 > > SHA512: > > > > > 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5 > > > > 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 > > > > 186 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353069 > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)
+1 (binding) Ran through release helper and tested various flows including verifying NIFI-11621 [1] for nested array inference and NIFI-11653 [2] for removing H2 support for DBCPConnectionPool. Also tested some version control capability for NiFi Registry. Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f) Maven home: /Users/mburgess/.sdkman/candidates/maven/current Java version: 11.0.19, vendor: Eclipse Adoptium, runtime: /Users/mburgess/.sdkman/candidates/java/11.0.19-tem Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "13.4", arch: "aarch64", family: "mac" Thanks for RM'ing Joe! [1] https://issues.apache.org/jira/browse/NIFI-11621 [2] https://issues.apache.org/jira/browse/NIFI-11653 On Tue, Jun 6, 2023 at 5:38 PM Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.22.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1228 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1 > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > Checksums of nifi-1.22.0-source-release.zip: > SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743 > SHA512: > 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5 > > 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 > > 186 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353069 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)
+1 (non-binding) verified source release sha256/512 checksums successfully ran buildusing:Apache Maven 3.6.3 Java openjdk version: 11.0.17linux kernel 3.10.0-1160 VerifiedNIFI-11570 Bulletin causes UI to think it cannot refreshNIFI-11392 NiFi does not stop timely when using CRON schedulingNIFI-11109 registry client class name modified in flow.json/xml when missing nifi-flow-registry-client-nar Ran some simple flows successfully. Noticed that what appears to be temporary file is being created in nifi root. Created https://issues.apache.org/jira/browse/NIFI-11660This is not a blocker. Also, noticed that MonitorMemory has difficulty running when scheduled as a cron.Created https://issues.apache.org/jira/browse/NIFI-11661Also not a blocker. Thank you for the upcoming release! Nissim Shiman On Tuesday, June 6, 2023 at 09:38:43 PM UTC, Joe Witt wrote: Hello, I am pleased to be calling this vote for the source release of Apache NiFi 1.22.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1228 The source being voted upon and the convenience binaries can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1 The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 Checksums of nifi-1.22.0-source-release.zip: SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743 SHA512: 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5 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 186 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353069 Release note highlights can be found here: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)
Hello, +1 non-binding Run through the verification process. Everything checks out well. Built NiFi with java version 1.8.0_362-8u372-ga~us1-0ubuntu1~22.04-b09 and apache-maven-3.9.2. Started NiFi and created basic flows. Verified - DBCP Verification Error - Fails to configure data source[1] - Bulletin causes UI to think it cannot refresh [2] - Expose JMX metrics from NiFi JVM [3] Tested new ModifyCompression Processor[4]. (My concern on this is that when you specify an incompatible input compression strategy, the processing fails with no useful message for the user to do the needful). It does not seem to be a blocker to me for the release. Thanks Joe for RM'ing. [1] https://issues.apache.org/jira/browse/NIFI-11547 [2] https://issues.apache.org/jira/browse/NIFI-11560 [3] https://issues.apache.org/jira/browse/NIFI-11385 [4] https://issues.apache.org/jira/browse/NIFI-11466 On Wed, Jun 7, 2023 at 12:38 AM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.22.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1228 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1 > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8 > > Checksums of nifi-1.22.0-source-release.zip: > SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743 > SHA512: > > 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5 > > 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 > > 186 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353069 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
