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... >
