Jira contributor access
Hello my username on Jira is "hellznrg". I would like to contribute to development on nifi-registry. Thanks -- Nesa Simon David Mobile: 0434059978
Re: [VOTE] Release Apache NiFi 1.16.1
+1 (binding) - Followed the release helper guide - Tested an insecure single instance with a simple flow on ubuntu 20.04, on Java 8 Thanks, Marton On Thu, 28 Apr 2022 at 20:36, Andrew Lim wrote: > > +1 (binding) > > -Ran full clean install on OS X (Catalina 10.15.7, OpenJDK version 1.8.0_252) > -Tested secure NiFi with secure NiFi Registry > -Ran basic flows successfully; tested basic versioned flow functionality > -Reviewed/tested Core UI fixes > > Drew > > > On Apr 25, 2022, at 2:29 PM, Joe Witt wrote: > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache NiFi > > 1.16.1. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1200 > > > > The source being voted upon and the convenience binaries can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.1/ > > > > 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.16.1-RC1 > > The Git commit ID is 81166797e552b9d14b482807632f2f04321b2018 > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81166797e552b9d14b482807632f2f04321b2018 > > > > Checksums of nifi-1.16.1-source-release.zip: > > SHA256: 2c39b45ba8eec42d601d5c9facad623d14660dd209c011b4a13b2b559b9f3e32 > > SHA512: > > cd670ab558937cac709dea0b4be3351559f57c9e9aedf54d5153706eee386a021262ef199e2bf9485763cf955931edfd6a24ca1c5a0748a77e3eeb91c490cbda > > > > 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 > > > > 83 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351504 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.1 > > > > 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.16.1 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.16.1
+1 (binding) -Ran full clean install on OS X (Catalina 10.15.7, OpenJDK version 1.8.0_252) -Tested secure NiFi with secure NiFi Registry -Ran basic flows successfully; tested basic versioned flow functionality -Reviewed/tested Core UI fixes Drew > On Apr 25, 2022, at 2:29 PM, Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.16.1. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1200 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.1/ > > 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.16.1-RC1 > The Git commit ID is 81166797e552b9d14b482807632f2f04321b2018 > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81166797e552b9d14b482807632f2f04321b2018 > > Checksums of nifi-1.16.1-source-release.zip: > SHA256: 2c39b45ba8eec42d601d5c9facad623d14660dd209c011b4a13b2b559b9f3e32 > SHA512: > cd670ab558937cac709dea0b4be3351559f57c9e9aedf54d5153706eee386a021262ef199e2bf9485763cf955931edfd6a24ca1c5a0748a77e3eeb91c490cbda > > 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 > > 83 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351504 > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.1 > > 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.16.1 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: Configurable default connection Prioritizer
Hi Mark, I searched and didn't see a ticket. I created one here: https://issues.apache.org/jira/browse/NIFI-9974 | Default Prioritizer for new Relationships Thanks, Ryan On Fri, Apr 15, 2022 at 10:24 AM Mark Bean wrote: > I like the idea. I'm thinking about how it would be implemented in the UI > (and API). Specifically, I'm comparing this feature of setting the > prioritizer to setting default connection properties via the configuration > of a process group. For the default connection properties, updates to the > process group configuration only change the default settings for any new > connection created; it does not affect existing connections. This was > intentional because it seemed heavy-handed to apply such settings to all > existing connections - especially expiration settings which could result in > data loss. > > However, the recommendation here is for actively changing the prioritizer > in all existing connections (and potentially nested connections in child > process groups). I understand the benefit and use case, but it seems the > two modification styles (new connections or existing connections) would > easily become confused. > > Would a checkbox for "apply prioritizer to all existing connections" be > appropriate? And, if so, we still need to somehow make it clear that this > applies to just prioritizer settings. I do not believe we want the other > connection settings to be recursively applied to existing connections. > > Do we want to introduce a new context menu item for process groups, > "Connection Settings" or something similar? > > Is there a JIRA ticket for this proposed new feature? > > On Tue, Apr 12, 2022 at 11:48 PM Ryan Hendrickson < > ryan.andrew.hendrick...@gmail.com> wrote: > > > @Bryan - Correct, everything is still per queue, just with that > convenience > > feature. > > > > Totally agree with @Salvatore too. I hadn't even thought of nested > process > > groups. > > > > On Tue, Apr 12, 2022 at 10:14 PM Salvatore > > wrote: > > > > > #2 would definitely be convenient. Maybe also include an option whether > > to > > > recurse down through nested process groups, or just apply to the > selected > > > process group. > > > > > > On Wed, 13 Apr 2022 at 06:05, Bryan Bende wrote: > > > > > > > Makes sense. For # 2, it is still per queue with an "Apply All" > > > > convenience right? Just trying to differentiate with prioritizing > > > > across all queues. > > > > > > > > On Tue, Apr 12, 2022 at 3:22 PM Ryan Hendrickson > > > > wrote: > > > > > > > > > > I see two things as particularly useful... > > > > > > > > > > 1) Default Prioritizer for new Relationships (Bound to a process > > > group, > > > > > similar to how the "Default FlowFile Expiration" can be changed). > > > > > 2) Applying a prioritizer to an entire Process Group as a one-time > > > > action. > > > > > > > > > > Some background... I'm hand-converting two super-legacy v0.7.3 > > canvases > > > > to > > > > > v1.15.3. Part of that is applying flow priorities all over the > place > > > in > > > > > the new system. Probably not a common task, but I could see this > > > feature > > > > > being useful for other week-to-week work too. > > > > > > > > > > Ryan > > > > > > > > > > On Tue, Apr 12, 2022 at 1:32 PM Bryan Bende > > wrote: > > > > > > > > > > > I think there are two different concepts here... The original > > > > > > discussion is just about default settings for new connections. > The > > > > > > idea in NIFI-6831 is about prioritizing data across multiple > > queues, > > > > > > either for all of nifi or within a given process group. > > > > > > > > > > > > > > > > > > On Tue, Apr 12, 2022 at 1:13 PM Mark Bean > > > > > wrote: > > > > > > > > > > > > > > We experimented with the idea of a custom "Global Prioritizer". > > One > > > > of > > > > > > the > > > > > > > problems with this approach is that it ran the risk of breaking > > the > > > > > > > multi-tenancy philosophy. If there were a truly global > priority, > > it > > > > would > > > > > > > affect all flows, each may have different priority rules. > > However, > > > if > > > > > > this > > > > > > > could be applied only at the process group level, it might have > > > legs. > > > > > > > > > > > > > > You can follow the initial approach to such a mechanism in the > > JIRA > > > > > > ticket. > > > > > > > https://issues.apache.org/jira/browse/NIFI-6831 > > > > > > > > > > > > > > > > > > > > > On Tue, Apr 12, 2022 at 12:06 PM Ryan Hendrickson < > > > > > > > ryan.andrew.hendrick...@gmail.com> wrote: > > > > > > > > > > > > > > > I just went to the config button in my process group, hoping > to > > > > set all > > > > > > > > relationships in there to priority first Lots of right > > > > clicking & > > > > > > > > dragging instead. > > > > > > > > > > > > > > > > +1 for an approach like that. > > > > > > > > > > > > > > > > On Tue, Apr 12, 2022 at 11:44 AM Joe Witt < > joe.w...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache NiFi 1.16.1
+1 (binding) Went through the usual steps. Deployed a secured cluster with secured NiFi Registry in GCP. Deployed usual/common flows. Looking good to me. Thanks Joe for taking care of this release. Pierre Le jeu. 28 avr. 2022 à 00:52, Peter Turcsanyi a écrit : > +1 (non-binding) > > Ran through the release helper. Built NiFi on Ubuntu 20.04 with Java 8 > (jdk8u322-b06) and Java 11 (jdk-11.0.14.1+1). > > Tested Stateless NiFi via ExecuteStateless and Kafka Connector using Java > 8, 11 and 17 runtimes. Verified: > - NIFI-9834: ExecuteStateless fails when the output FlowFile has no > content > - NIFI-9861: Stateless ClassLoader isolation does not work on Java 11 > > Regards, > Peter Turcsanyi > > On Wed, Apr 27, 2022 at 9:02 PM Nathan Gough wrote: > > > +1 (non-binding), ran a 3 node cluster using external ZK with some simple > > test flows. Ran NiFi with Google OIDC auth. Checked hashes and other > files. > > > > On Wed, Apr 27, 2022 at 10:24 AM Mike Thomsen > > wrote: > > > > > +1 (binding) Ran a simple tika extraction flow on PDFs and DOCX files. > > > Worked fine. Saved that flow into the NiFi Registry. > > > > > > On Tue, Apr 26, 2022 at 4:47 PM Matt Burgess > > wrote: > > > > > > > > +1 (binding) > > > > > > > > Ran through release helper, tested various flows including version > > > > control with the Registry, InvokeScriptedProcessor, Relationship > > > > retry, etc. I did create [1] for MiNiFi but since there's a > > > > workaround it's not a dealbreaker IMO, I'm already working on it for > > > > 1.17.0. > > > > > > > > Thanks for RM'ing Joe! > > > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-9967 > > > > > > > > On Mon, Apr 25, 2022 at 2:29 PM Joe Witt wrote: > > > > > > > > > > Hello, > > > > > > > > > > I am pleased to be calling this vote for the source release of > Apache > > > NiFi > > > > > 1.16.1. > > > > > > > > > > The source zip, including signatures, digests, etc. can be found > at: > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1200 > > > > > > > > > > The source being voted upon and the convenience binaries can be > found > > > at: > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.1/ > > > > > > > > > > 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.16.1-RC1 > > > > > The Git commit ID is 81166797e552b9d14b482807632f2f04321b2018 > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81166797e552b9d14b482807632f2f04321b2018 > > > > > > > > > > Checksums of nifi-1.16.1-source-release.zip: > > > > > SHA256: > > > 2c39b45ba8eec42d601d5c9facad623d14660dd209c011b4a13b2b559b9f3e32 > > > > > SHA512: > > > > > > > > > > > cd670ab558937cac709dea0b4be3351559f57c9e9aedf54d5153706eee386a021262ef199e2bf9485763cf955931edfd6a24ca1c5a0748a77e3eeb91c490cbda > > > > > > > > > > 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 > > > > > > > > > > 83 issues were closed/resolved for this release: > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351504 > > > > > Release note highlights can be found here: > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.1 > > > > > > > > > > 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.16.1 > > > > > [ ] +0 no opinion > > > > > [ ] -1 Do not release this package because... > > > > > >
