Re: [VOTE] Release Apache NiFi Registry 0.7.0
+1 (binding) Verified build on Java11, signatures, hashes. Lic and notice looks good. Started, was able to create buckets and save flow. On Sat, Jul 18, 2020 at 3:19 PM Tony Kurc wrote: > +1 (binding) > > Built on an ubuntu 16.04 x64 w/openjdk 11 without issues. Verified > signatures and hashes. Saw no issues with LICENSE or NOTICE. > > Tony > > On Fri, Jul 17, 2020 at 10:10 PM Marc Parisi wrote: > > > +1 binding > > > > Verified sigs and hashes > > > > Built and run on Linux LXC (Java 11) w/ Secured Apache NiFi built and run > > in the same container. All looked good > > > > Perused L and it looked good. > > > > Thanks, > > Marc > > > > On Fri, Jul 17, 2020 at 5:48 PM Peter Turcsanyi > > wrote: > > > > > +1 (non-binding) > > > > > > - verified signatures and checksums > > > - built with Java 8 (empty local maven repo, OS: Ubuntu 18) > > > - run NiFi Registry and connected to it from NiFi 1.11.4 (unsecure), > > > performed some tests > > > - download the convenience binary and tested a few things on it too > > > > > > Thanks, > > > Peter > > > > > > On Fri, Jul 17, 2020 at 7:20 PM Marton Szasz > wrote: > > > > > > > +1 (non-binding) > > > > > > > > Followed the verification guide, migrated a test deployment using > > > > GitFlowPersistenceProvider from 0.6.0, then tested MiNiFi C++ C2 flow > > > > update using the new registry version. > > > > > > > > Thanks, > > > > Marton > > > > > > > > On Fri, 17 Jul 2020 at 18:36, Mark Payne > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > Verified full build with contrib check, deployed and performed some > > > > tests, > > > > > verifying that the FlowFiles concurrency and outbound policy was > > > properly > > > > > stored and retrieved. > > > > > > > > > > Thanks > > > > > -Mark > > > > > > > > > > > > > > > > On Jul 17, 2020, at 11:55 AM, Pierre Villard < > > > > > pierre.villard...@gmail.com> wrote: > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > * went through the usual release verification steps (signatures, > > > build, > > > > > > contrib check, licenses) > > > > > > * deployed a local NR 0.7.0 instance with a single local NiFi > > > > > > 1.12.0-SNAPSHOT (non secure) > > > > > > > > > > > > Thanks Bryan for taking care of this! > > > > > > > > > > > > Le ven. 17 juil. 2020 à 17:46, Matt Burgess < > mattyb...@apache.org> > > a > > > > > écrit : > > > > > > > > > > > >> +1 (binding), verified hashes and commit ID, tested a few things > > on > > > an > > > > > >> unsecured instance. Thanks for RM'ing Bryan! > > > > > >> > > > > > >> On Wed, Jul 15, 2020 at 11:32 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
Re: Failing to update custom processor properties names, displayNames, etc.
Andy,
You're right. I was a caching issue with Chrome. I don't know why I
didn't think to try that--forest for the trees, I guess. Thank you.
Russ
On 7/17/20 5:58 PM, Andy LoPresto wrote:
Russell,
Have you verified this is not a browser caching issue? They are pernicious and
it sounds like this could be an example. If you’re sure it’s not, verify the
API calls using your browser’s Developer Tools to see what properties are
actually being returned by the server when inspecting a component to see if the
correct values are present. If so, it’s likely a UI bug, and if not, the new
code is not being properly loaded/used by NiFi’s server application.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
On Jul 17, 2020, at 3:48 PM, Russell Bateman wrote:
If I have changed a custom processor's PropertyDescriptor.nameand/or
.displayName,including changes I have made to my /additionalDetails.html, /and
I have:
- removed that processor from my test flow or removed /flow.xml.gz/ altogether
- removed my NAR from /${NIFI_ROOT}///custom-lib/ and bounced NiFi with the new
custom NAR copied
yet nothing changes (in usage or in additional details), what am I overlooking?
Let's set aside the vaguely confusing semantic distinction between nameand
displayName, I just want NiFi to forget my new custom processor completely and
then accept my new version as if brand new including all the changes I have
made.
Thanks for any suggestions.
Re: [VOTE] Release Apache NiFi Registry 0.7.0
+1 (binding) Built on an ubuntu 16.04 x64 w/openjdk 11 without issues. Verified signatures and hashes. Saw no issues with LICENSE or NOTICE. Tony On Fri, Jul 17, 2020 at 10:10 PM Marc Parisi wrote: > +1 binding > > Verified sigs and hashes > > Built and run on Linux LXC (Java 11) w/ Secured Apache NiFi built and run > in the same container. All looked good > > Perused L and it looked good. > > Thanks, > Marc > > On Fri, Jul 17, 2020 at 5:48 PM Peter Turcsanyi > wrote: > > > +1 (non-binding) > > > > - verified signatures and checksums > > - built with Java 8 (empty local maven repo, OS: Ubuntu 18) > > - run NiFi Registry and connected to it from NiFi 1.11.4 (unsecure), > > performed some tests > > - download the convenience binary and tested a few things on it too > > > > Thanks, > > Peter > > > > On Fri, Jul 17, 2020 at 7:20 PM Marton Szasz wrote: > > > > > +1 (non-binding) > > > > > > Followed the verification guide, migrated a test deployment using > > > GitFlowPersistenceProvider from 0.6.0, then tested MiNiFi C++ C2 flow > > > update using the new registry version. > > > > > > Thanks, > > > Marton > > > > > > On Fri, 17 Jul 2020 at 18:36, Mark Payne wrote: > > > > > > > +1 (binding) > > > > > > > > Verified full build with contrib check, deployed and performed some > > > tests, > > > > verifying that the FlowFiles concurrency and outbound policy was > > properly > > > > stored and retrieved. > > > > > > > > Thanks > > > > -Mark > > > > > > > > > > > > > On Jul 17, 2020, at 11:55 AM, Pierre Villard < > > > > pierre.villard...@gmail.com> wrote: > > > > > > > > > > +1 (binding) > > > > > > > > > > * went through the usual release verification steps (signatures, > > build, > > > > > contrib check, licenses) > > > > > * deployed a local NR 0.7.0 instance with a single local NiFi > > > > > 1.12.0-SNAPSHOT (non secure) > > > > > > > > > > Thanks Bryan for taking care of this! > > > > > > > > > > Le ven. 17 juil. 2020 à 17:46, Matt Burgess > a > > > > écrit : > > > > > > > > > >> +1 (binding), verified hashes and commit ID, tested a few things > on > > an > > > > >> unsecured instance. Thanks for RM'ing Bryan! > > > > >> > > > > >> On Wed, Jul 15, 2020 at 11:32 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... > > > > >> > > > > > > > > > > > > > >
