+1 binding Went through the usual steps of deploying a secured cluster with NiFi Registry and testing some flows.
Noticed a couple of things: - The delete-param CLI command is no longer working [1] - There are some lucene related warnings at provenance repo initialization that might require some attention at some point But nothing that could impact this release candidate. There is also one outstanding PR [2] that might introduce a breaking change depending on the approach we will take but I think we still have a bit of margin around such changes as we receive feedback from the larger community post 2.0 release for a potential 2.0.1 release. Thanks for taking care of the release David, great to see 2.0 finally going out! [1] https://issues.apache.org/jira/browse/NIFI-13924 [2] https://github.com/apache/nifi/pull/9347 Thanks, Pierre Le jeu. 24 oct. 2024 à 13:35, Ferenc Kis <briansolo1...@gmail.com> a écrit : > +1 (non-binding) > > Went through the helper guide, local maven repo cleaned up, full clean > build with contrib check, verified signatures and hashes > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /Users/fkis/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1 > Java version: 21, vendor: Azul Systems, Inc., runtime: > /Users/fkis/.sdkman/candidates/java/21-zulu/zulu-21.jdk/Contents/Home > Default locale: en_HU, platform encoding: UTF-8 > OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac" > > Validations performed: > - Started NiFi, created a simple flow with ListenHTTP and Input Port. > Validated ListenHTTP processor is able to receive data > - Started MiNiFi Java: > * created a simple GenerateFlowFile -> InvokeHttp flow and > GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > protocol > * Validated that connectivity between NiFi and MiNiFi works via both > InvokeHTTP and S2S > - NIFI-13883 [MiNiFI][C2] Fix MiNiFI recovery if exception happens on > config update > - NIFI-13846 [MiNiFi] Create default parameter context to enable running > empty flows received via C2 > - NIFI-13812 [MiNiFi][C2] Add component type into Agent Manifest Hash > calculation > - NIFI-13746 [MiNiFi] Override controller services SSL Context Service with > parent SSL Context Service. Parent SSL Context Service is added to root > process group instead of management controller services > - NIFI-13762 Expose processor metrics as a part of FlowInfo > - NIFI-13614: populate failure cause in operation state > - NIFI-13635 Expose processor bulletins as a part of FlowInfo > - NIFI-13541 [MiNiFi] Validate flow during startup > - NIFI-13568 MiNiFi Fix concurrent SAXParser issue in manifest parsing > - NIFI-13436 Retain queue for non-modified connections during MiNiFi flow > update > > Thanks for RMing David! > > Regards > Ferenc > > On Wed, Oct 23, 2024 at 9:46 PM Nissim Shiman <nshi...@yahoo.com.invalid> > wrote: > > > +1 (non-binding) > > > > checksums are good > > > > Compiled with > > Apache Maven 3.9.9 1.8.0_422 (openjdk) RHEL 8 > > > > Ran some basic flows Upgraded nifi registry (with pre-existing versioned > > flows) from 1.27 to 1.28 successfully. Created new PGs from versioned > > flows. Pushed new versions of flows to registry. > > > > Thank you Ferenc and team for the upcoming release. > > > > Thanks, > > Nissim Shiman > > > > > > On Tuesday, October 22, 2024 at 10:45:12 AM UTC, Ferenc Kis < > > briansolo1...@gmail.com> wrote: > > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.28.0. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are available > on > > the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.28.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1289 > > > > Git Tag: nifi-1.28.0-RC1 > > Git Commit ID: 8ecf23e77c8ca828a77f3b84554ed3347d8f7fa2 > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/8ecf23e77c8ca828a77f3b84554ed3347d8f7fa2 > > > > Checksums of nifi-1.28.0-source-release.zip > > > > SHA256: 96ddd83ee11f6dd0889ff2f4b4112487f021b2b3f0573d7c0eeff40672620e93 > > SHA512: > > > > > 22f0051b5e4a41b913e36f1fa2fabe6871471b0a4a51f3673b2fcc453382cd5d6eb132f7a6686ecdc065c295a2cfaf8199a653b822837f73a23016b6ae4bd143 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/briansolo1985.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 63 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354883 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.28.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.28.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > > > > > On Wed, Oct 23, 2024 at 8:41 PM Nissim Shiman <nshi...@yahoo.com.invalid> > wrote: > > > Thank you Matt for verifying this (and putting in a ticket to track) > > > > > > +1 (non-binding) > > > > checksum looks good > > > > Compiled withApache Maven 3.9.9Java 21.0.4 (openjdk) RHEL 8 > > > > Ran some simple flows. Verified nifi registry import from 1.27 to 2.0.0 > > works. Versioned some flows. Imported those flows back to graph. > > > > > > Ran into non blocker issue to Improve cursor visibility for editing > > processor properties https://issues.apache.org/jira/browse/NIFI-13925 > > > > Also, ran into issue where there can be difficulty importing from nifi > > registry when flows have different number of versions. Thank you Matt > for > > verifying this. > > > > > > Thank you David and team, > > > > Nissim Shiman > > > > On Wednesday, October 23, 2024 at 05:55:18 PM UTC, Matt Gilman < > > matt.c.gil...@gmail.com> wrote: > > > > Thanks for reporting this Nissim. I've filed [1] to track the issue. > > > > Matt > > > > [1] https://issues.apache.org/jira/browse/NIFI-13926 > > > > On Wed, Oct 23, 2024 at 12:47 PM Nissim Shiman <nshi...@yahoo.com.invalid > > > > wrote: > > > > > Team, > > > > > > > > > I am running into an issue with the "Import from Registry" option from > > the > > > nifi ui when pulling a flow from nifi registry when there are multiple > > > flows in the registry, with each flow having a different number of > > versions. > > > > > > > > > If the first flow is chosen, it works fine. (i.e. whatever choice is > > used > > > for registry and bucket, there will be some flow that is first on the > > > dropdown list. That import will be fine.) > > > > > > If another flow is chosen there is an error in ui saying > > > Unable to obtain listing of versions for bucket with ID <id> and flow > > with > > > ID <id>: Invalid branch, NiFi Registry client only supports the default > > > branch 'main' > > > > > > > > > Another flow is still able to be chosen, but the version will be > whatever > > > the default (latest) version of the first choice on the dropdown menu - > > not > > > the latest version for that flow. > > > > > > > > > If the chosen flow has less versions than the first choice on the > > > dropdown, then it is not able to be imported to the nifi ui. > > > The ui message will be: > > > The Flow Registry with ID <id> reports that no Flow exists with Bucket > > > <id>, Flow <id> Version <number greater than 1> > > > > > > > > > I am wondering if anyone else is seeing this. > > > > > > > > > Thanks, > > > > > > Nissim Shiman > > > > > > > > > On Tuesday, October 22, 2024 at 05:02:06 AM UTC, David Handermann < > > > exceptionfact...@apache.org> wrote: > > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi 2.0.0. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on the and the convenience binaries are > > > available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1293/ > > > > > > Git Tag: nifi-2.0.0-RC1 > > > Git Commit ID: 34160740980c2d9d5cd0a6c399e09c2bd06d5acb > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/34160740980c2d9d5cd0a6c399e09c2bd06d5acb > > > > > > Checksums of nifi-2.0.0-source-release.zip > > > > > > SHA512: > > > > > > 09f37a4f8fd798a8b067d7970ea571ebc2f729c98cffd427e00d41a0b9312bbcd6b074a1f9109304939b89b5074ccdc48feeff712ecce3f3b1e1a358da7e4a57 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 323 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354889 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.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-2.0.0 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
