Re: [RESULT][VOTE] Release Apache NiFi 1.12.0
yeah!! On Tue, Aug 18, 2020 at 4:50 PM Mark Payne wrote: > Awesome! Thanks for doing all the work to get the release out, Joe! > > -Mark > > Sent from my iPhone > > > On Aug 18, 2020, at 4:48 PM, Joe Witt wrote: > > > > Apache NiFi Community, > > > > I am pleased to announce that the 1.12.0 release of Apache NiFi passes > with > >11 +1 (binding) votes > >9 +1 (non-binding) votes > >0 0 votes > >0 -1 votes > > > > Thanks to all who helped make this release possible. Pretty awesome turn > > out on the vote so thank you! > > > > Here is the PMC vote thread: > > > https://lists.apache.org/thread.html/r42081bf5f6a394be91381dedb477c6ed666b1dc2251dbd0b59b6b252%40%3Cdev.nifi.apache.org%3E > > > > > >> On Tue, Aug 18, 2020 at 1:44 PM Joe Witt wrote: > >> > >> +1 binding > >> > >>> On Tue, Aug 18, 2020 at 11:39 AM Marton Szasz > wrote: > >>> > >>> +1 (non-binding) > >>> > >>> Signature, hashes, commit ID, README, LICENSE and NOTICE all look OK. > >>> Built > >>> and tested with Java 8, ran a simple MiNiFi C++ HTTP S2S -> NiFi flow. > >>> > >>> Thanks, > >>> Marton > >>> > >>> > On Mon, 17 Aug 2020 at 15:35, wrote: > >>> > +1 (non-binding) > > Compile and ran with Amazon Correttto Java 8 on OSX. I had an issue > getting site-to-site to work between NiFi 1.11.4 and NiFi 1.12.0 in > RAW > mode (non-secure) and had to switch to using HTTP. The message on the > Remote Process Group read “Remote instance is not configured to allow > >>> RAW > Site-to-site communication at this time". Are new configurations > >>> required > to transmit Iva Site-to-site in RAW mode? I didn’t see anything in > the > docs or online. Note that I was running both versions on the same > >>> computer > and modified the one instance with the following properties. > > nifi.web.http.port=8081 > nifi.remote.input.socket.port=9991 > > Rick > > -- > Richard St. John, PhD > Asymmetrik > AGILITY | EXPERIENCE | RESULTS > 308 Sentinel Drive, Suite 400 > Annapolis Junction, MD 20701 > On Aug 16, 2020, 11:03 PM -0400, Chad Zobrisky , > wrote: > > +1 (non-binding) > > > > Ran through the release helper, everything looks good. > > Full build on java8 in wsl, ubuntu. > > Verified basic functionality in single node and 5 cluster docker > > configuration. > > > > - Chad > > > > > > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi > >>> wrote: > > > >> +1 (binding ) > >> > >> Ran through helper guide with clean build env . Ran flows that > >>> ingest > and > >> query Apache hbase and accumulo from a 10 VM secured cluster in my > local > >> environment with jdk11. > >> > >> Thanks, > >> Marc > >> > >> > >> On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada > wrote: > >> > >>> +1 (non-binding) > >>> > >>> Verified signatures and hashes. > >>> Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8. > >>> Set up a 3-node cluster. > >>> Tested several flows. > >>> > >>> Thanks, > >>> Kotaro > >>> > >>> > >>> On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee < > >>> joey.fra...@icloud.com > >>> .invalid> > >>> wrote: > >>> > +1 (non-binding) > > Verified commit id, checksums, and signatures > Successfully built and ran tests on Linux with Java 1.8.0_252 > >>> and > Java > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS > Ran data flows on standalone and cluster > Verified JMS improvements, InvokeHTTP changes, and Azure > integration in > commercial and gov regions > > -joey > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows < > rob.fell...@gmail.com > >>> , > wrote: > > + 1 (non-binding) > > > > Ran through the release helper, verified checksums and sigs. > > Full build with java 11 > > Verified basic app usage/functionality. > > > > > > > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid < > >>> mua...@gmail.com> > >> wrote: > > > >> +1 (non-binding) > >> Ran through the release helper. Deployed a 10 node cluster > >>> on > Azure > >>> and > >> verified the functionality of new ADLS processors with a > standard > >>> flow. > >> Looks good to me. > >> > >> Thanks, > >> Muazma > >> > >> On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim < > andrewlim.apa...@gmail.com> > >> wrote: > >> > >>> +1 (binding) > >>> > >>> -Ran full clean install on OS X (Catalina 10.15.2) > >>> -Tested secure NiFi with secure NiFi Registry 0.7.0 > >>> -Ran basic flows successfully; tested basic versioned flow >
Re: [RESULT][VOTE] Release Apache NiFi 1.12.0
Awesome! Thanks for doing all the work to get the release out, Joe! -Mark Sent from my iPhone > On Aug 18, 2020, at 4:48 PM, Joe Witt wrote: > > Apache NiFi Community, > > I am pleased to announce that the 1.12.0 release of Apache NiFi passes with >11 +1 (binding) votes >9 +1 (non-binding) votes >0 0 votes >0 -1 votes > > Thanks to all who helped make this release possible. Pretty awesome turn > out on the vote so thank you! > > Here is the PMC vote thread: > https://lists.apache.org/thread.html/r42081bf5f6a394be91381dedb477c6ed666b1dc2251dbd0b59b6b252%40%3Cdev.nifi.apache.org%3E > > >> On Tue, Aug 18, 2020 at 1:44 PM Joe Witt wrote: >> >> +1 binding >> >>> On Tue, Aug 18, 2020 at 11:39 AM Marton Szasz wrote: >>> >>> +1 (non-binding) >>> >>> Signature, hashes, commit ID, README, LICENSE and NOTICE all look OK. >>> Built >>> and tested with Java 8, ran a simple MiNiFi C++ HTTP S2S -> NiFi flow. >>> >>> Thanks, >>> Marton >>> >>> On Mon, 17 Aug 2020 at 15:35, wrote: >>> +1 (non-binding) Compile and ran with Amazon Correttto Java 8 on OSX. I had an issue getting site-to-site to work between NiFi 1.11.4 and NiFi 1.12.0 in RAW mode (non-secure) and had to switch to using HTTP. The message on the Remote Process Group read “Remote instance is not configured to allow >>> RAW Site-to-site communication at this time". Are new configurations >>> required to transmit Iva Site-to-site in RAW mode? I didn’t see anything in the docs or online. Note that I was running both versions on the same >>> computer and modified the one instance with the following properties. nifi.web.http.port=8081 nifi.remote.input.socket.port=9991 Rick -- Richard St. John, PhD Asymmetrik AGILITY | EXPERIENCE | RESULTS 308 Sentinel Drive, Suite 400 Annapolis Junction, MD 20701 On Aug 16, 2020, 11:03 PM -0400, Chad Zobrisky , wrote: > +1 (non-binding) > > Ran through the release helper, everything looks good. > Full build on java8 in wsl, ubuntu. > Verified basic functionality in single node and 5 cluster docker > configuration. > > - Chad > > > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi >>> wrote: > >> +1 (binding ) >> >> Ran through helper guide with clean build env . Ran flows that >>> ingest and >> query Apache hbase and accumulo from a 10 VM secured cluster in my local >> environment with jdk11. >> >> Thanks, >> Marc >> >> >> On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada wrote: >> >>> +1 (non-binding) >>> >>> Verified signatures and hashes. >>> Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8. >>> Set up a 3-node cluster. >>> Tested several flows. >>> >>> Thanks, >>> Kotaro >>> >>> >>> On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee < >>> joey.fra...@icloud.com >>> .invalid> >>> wrote: >>> +1 (non-binding) Verified commit id, checksums, and signatures Successfully built and ran tests on Linux with Java 1.8.0_252 >>> and Java 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS Ran data flows on standalone and cluster Verified JMS improvements, InvokeHTTP changes, and Azure integration in commercial and gov regions -joey On Aug 14, 2020, 1:31 PM -0700, Robert Fellows < rob.fell...@gmail.com >>> , wrote: > + 1 (non-binding) > > Ran through the release helper, verified checksums and sigs. > Full build with java 11 > Verified basic app usage/functionality. > > > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid < >>> mua...@gmail.com> >> wrote: > >> +1 (non-binding) >> Ran through the release helper. Deployed a 10 node cluster >>> on Azure >>> and >> verified the functionality of new ADLS processors with a standard >>> flow. >> Looks good to me. >> >> Thanks, >> Muazma >> >> On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim < andrewlim.apa...@gmail.com> >> wrote: >> >>> +1 (binding) >>> >>> -Ran full clean install on OS X (Catalina 10.15.2) >>> -Tested secure NiFi with secure NiFi Registry 0.7.0 >>> -Ran basic flows successfully; tested basic versioned flow functionality >>> -Reviewed documentation updates. Lots of a great >>> additions in >> this >> release! >>> -Reviewed core UI fixes and improvements. Verified that >> controller >>> services are searchable [1], but filed a Jira for the navigation >> to the >>> controller service being broken
[RESULT][VOTE] Release Apache NiFi 1.12.0
Apache NiFi Community, I am pleased to announce that the 1.12.0 release of Apache NiFi passes with 11 +1 (binding) votes 9 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Pretty awesome turn out on the vote so thank you! Here is the PMC vote thread: https://lists.apache.org/thread.html/r42081bf5f6a394be91381dedb477c6ed666b1dc2251dbd0b59b6b252%40%3Cdev.nifi.apache.org%3E On Tue, Aug 18, 2020 at 1:44 PM Joe Witt wrote: > +1 binding > > On Tue, Aug 18, 2020 at 11:39 AM Marton Szasz wrote: > >> +1 (non-binding) >> >> Signature, hashes, commit ID, README, LICENSE and NOTICE all look OK. >> Built >> and tested with Java 8, ran a simple MiNiFi C++ HTTP S2S -> NiFi flow. >> >> Thanks, >> Marton >> >> >> On Mon, 17 Aug 2020 at 15:35, wrote: >> >> > +1 (non-binding) >> > >> > Compile and ran with Amazon Correttto Java 8 on OSX. I had an issue >> > getting site-to-site to work between NiFi 1.11.4 and NiFi 1.12.0 in RAW >> > mode (non-secure) and had to switch to using HTTP. The message on the >> > Remote Process Group read “Remote instance is not configured to allow >> RAW >> > Site-to-site communication at this time". Are new configurations >> required >> > to transmit Iva Site-to-site in RAW mode? I didn’t see anything in the >> > docs or online. Note that I was running both versions on the same >> computer >> > and modified the one instance with the following properties. >> > >> > nifi.web.http.port=8081 >> > nifi.remote.input.socket.port=9991 >> > >> > Rick >> > >> > -- >> > Richard St. John, PhD >> > Asymmetrik >> > AGILITY | EXPERIENCE | RESULTS >> > 308 Sentinel Drive, Suite 400 >> > Annapolis Junction, MD 20701 >> > On Aug 16, 2020, 11:03 PM -0400, Chad Zobrisky , >> > wrote: >> > > +1 (non-binding) >> > > >> > > Ran through the release helper, everything looks good. >> > > Full build on java8 in wsl, ubuntu. >> > > Verified basic functionality in single node and 5 cluster docker >> > > configuration. >> > > >> > > - Chad >> > > >> > > >> > > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi >> wrote: >> > > >> > > > +1 (binding ) >> > > > >> > > > Ran through helper guide with clean build env . Ran flows that >> ingest >> > and >> > > > query Apache hbase and accumulo from a 10 VM secured cluster in my >> > local >> > > > environment with jdk11. >> > > > >> > > > Thanks, >> > > > Marc >> > > > >> > > > >> > > > On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada >> > wrote: >> > > > >> > > > > +1 (non-binding) >> > > > > >> > > > > Verified signatures and hashes. >> > > > > Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8. >> > > > > Set up a 3-node cluster. >> > > > > Tested several flows. >> > > > > >> > > > > Thanks, >> > > > > Kotaro >> > > > > >> > > > > >> > > > > On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee < >> joey.fra...@icloud.com >> > > > > .invalid> >> > > > > wrote: >> > > > > >> > > > > > +1 (non-binding) >> > > > > > >> > > > > > Verified commit id, checksums, and signatures >> > > > > > Successfully built and ran tests on Linux with Java 1.8.0_252 >> and >> > Java >> > > > > > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS >> > > > > > Ran data flows on standalone and cluster >> > > > > > Verified JMS improvements, InvokeHTTP changes, and Azure >> > integration in >> > > > > > commercial and gov regions >> > > > > > >> > > > > > -joey >> > > > > > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows < >> > rob.fell...@gmail.com >> > > > > , >> > > > > > wrote: >> > > > > > > + 1 (non-binding) >> > > > > > > >> > > > > > > Ran through the release helper, verified checksums and sigs. >> > > > > > > Full build with java 11 >> > > > > > > Verified basic app usage/functionality. >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid < >> mua...@gmail.com> >> > > > wrote: >> > > > > > > >> > > > > > > > +1 (non-binding) >> > > > > > > > Ran through the release helper. Deployed a 10 node cluster >> on >> > Azure >> > > > > and >> > > > > > > > verified the functionality of new ADLS processors with a >> > standard >> > > > > flow. >> > > > > > > > Looks good to me. >> > > > > > > > >> > > > > > > > Thanks, >> > > > > > > > Muazma >> > > > > > > > >> > > > > > > > On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim < >> > > > > > andrewlim.apa...@gmail.com> >> > > > > > > > wrote: >> > > > > > > > >> > > > > > > > > +1 (binding) >> > > > > > > > > >> > > > > > > > > -Ran full clean install on OS X (Catalina 10.15.2) >> > > > > > > > > -Tested secure NiFi with secure NiFi Registry 0.7.0 >> > > > > > > > > -Ran basic flows successfully; tested basic versioned flow >> > > > > > functionality >> > > > > > > > > -Reviewed documentation updates. Lots of a great >> additions in >> > > > this >> > > > > > > > release! >> > > > > > > > > -Reviewed core UI fixes and improvements. Verified that >> > > > controller >> > > > > > > > > services are searchable [1], but filed a Jira for the >>
Re: [VOTE] Release Apache NiFi 1.12.0
+1 binding On Tue, Aug 18, 2020 at 11:39 AM Marton Szasz wrote: > +1 (non-binding) > > Signature, hashes, commit ID, README, LICENSE and NOTICE all look OK. Built > and tested with Java 8, ran a simple MiNiFi C++ HTTP S2S -> NiFi flow. > > Thanks, > Marton > > > On Mon, 17 Aug 2020 at 15:35, wrote: > > > +1 (non-binding) > > > > Compile and ran with Amazon Correttto Java 8 on OSX. I had an issue > > getting site-to-site to work between NiFi 1.11.4 and NiFi 1.12.0 in RAW > > mode (non-secure) and had to switch to using HTTP. The message on the > > Remote Process Group read “Remote instance is not configured to allow RAW > > Site-to-site communication at this time". Are new configurations > required > > to transmit Iva Site-to-site in RAW mode? I didn’t see anything in the > > docs or online. Note that I was running both versions on the same > computer > > and modified the one instance with the following properties. > > > > nifi.web.http.port=8081 > > nifi.remote.input.socket.port=9991 > > > > Rick > > > > -- > > Richard St. John, PhD > > Asymmetrik > > AGILITY | EXPERIENCE | RESULTS > > 308 Sentinel Drive, Suite 400 > > Annapolis Junction, MD 20701 > > On Aug 16, 2020, 11:03 PM -0400, Chad Zobrisky , > > wrote: > > > +1 (non-binding) > > > > > > Ran through the release helper, everything looks good. > > > Full build on java8 in wsl, ubuntu. > > > Verified basic functionality in single node and 5 cluster docker > > > configuration. > > > > > > - Chad > > > > > > > > > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi > wrote: > > > > > > > +1 (binding ) > > > > > > > > Ran through helper guide with clean build env . Ran flows that ingest > > and > > > > query Apache hbase and accumulo from a 10 VM secured cluster in my > > local > > > > environment with jdk11. > > > > > > > > Thanks, > > > > Marc > > > > > > > > > > > > On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada > > wrote: > > > > > > > > > +1 (non-binding) > > > > > > > > > > Verified signatures and hashes. > > > > > Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8. > > > > > Set up a 3-node cluster. > > > > > Tested several flows. > > > > > > > > > > Thanks, > > > > > Kotaro > > > > > > > > > > > > > > > On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee < > joey.fra...@icloud.com > > > > > .invalid> > > > > > wrote: > > > > > > > > > > > +1 (non-binding) > > > > > > > > > > > > Verified commit id, checksums, and signatures > > > > > > Successfully built and ran tests on Linux with Java 1.8.0_252 and > > Java > > > > > > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS > > > > > > Ran data flows on standalone and cluster > > > > > > Verified JMS improvements, InvokeHTTP changes, and Azure > > integration in > > > > > > commercial and gov regions > > > > > > > > > > > > -joey > > > > > > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows < > > rob.fell...@gmail.com > > > > > , > > > > > > wrote: > > > > > > > + 1 (non-binding) > > > > > > > > > > > > > > Ran through the release helper, verified checksums and sigs. > > > > > > > Full build with java 11 > > > > > > > Verified basic app usage/functionality. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid > > > > > wrote: > > > > > > > > > > > > > > > +1 (non-binding) > > > > > > > > Ran through the release helper. Deployed a 10 node cluster on > > Azure > > > > > and > > > > > > > > verified the functionality of new ADLS processors with a > > standard > > > > > flow. > > > > > > > > Looks good to me. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Muazma > > > > > > > > > > > > > > > > On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim < > > > > > > andrewlim.apa...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > > > > > > > -Ran full clean install on OS X (Catalina 10.15.2) > > > > > > > > > -Tested secure NiFi with secure NiFi Registry 0.7.0 > > > > > > > > > -Ran basic flows successfully; tested basic versioned flow > > > > > > functionality > > > > > > > > > -Reviewed documentation updates. Lots of a great additions > in > > > > this > > > > > > > > release! > > > > > > > > > -Reviewed core UI fixes and improvements. Verified that > > > > controller > > > > > > > > > services are searchable [1], but filed a Jira for the > > navigation > > > > to > > > > > > the > > > > > > > > > controller service being broken [2]. > > > > > > > > > > > > > > > > > > Drew > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-5925 < > > > > > > > > > https://issues.apache.org/jira/browse/NIFI-5925> > > > > > > > > > [2] https://issues.apache.org/jira/browse/NIFI-7742 < > > > > > > > > > https://issues.apache.org/jira/browse/NIFI-7742> > > > > > > > > > > > > > > > > > > > On Aug 13, 2020, at 4:31 PM, Joe Witt < > joew...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > I am pleased to be calling this
Re: [VOTE] Release Apache NiFi 1.12.0
+1 (non-binding) Signature, hashes, commit ID, README, LICENSE and NOTICE all look OK. Built and tested with Java 8, ran a simple MiNiFi C++ HTTP S2S -> NiFi flow. Thanks, Marton On Mon, 17 Aug 2020 at 15:35, wrote: > +1 (non-binding) > > Compile and ran with Amazon Correttto Java 8 on OSX. I had an issue > getting site-to-site to work between NiFi 1.11.4 and NiFi 1.12.0 in RAW > mode (non-secure) and had to switch to using HTTP. The message on the > Remote Process Group read “Remote instance is not configured to allow RAW > Site-to-site communication at this time". Are new configurations required > to transmit Iva Site-to-site in RAW mode? I didn’t see anything in the > docs or online. Note that I was running both versions on the same computer > and modified the one instance with the following properties. > > nifi.web.http.port=8081 > nifi.remote.input.socket.port=9991 > > Rick > > -- > Richard St. John, PhD > Asymmetrik > AGILITY | EXPERIENCE | RESULTS > 308 Sentinel Drive, Suite 400 > Annapolis Junction, MD 20701 > On Aug 16, 2020, 11:03 PM -0400, Chad Zobrisky , > wrote: > > +1 (non-binding) > > > > Ran through the release helper, everything looks good. > > Full build on java8 in wsl, ubuntu. > > Verified basic functionality in single node and 5 cluster docker > > configuration. > > > > - Chad > > > > > > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi wrote: > > > > > +1 (binding ) > > > > > > Ran through helper guide with clean build env . Ran flows that ingest > and > > > query Apache hbase and accumulo from a 10 VM secured cluster in my > local > > > environment with jdk11. > > > > > > Thanks, > > > Marc > > > > > > > > > On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada > wrote: > > > > > > > +1 (non-binding) > > > > > > > > Verified signatures and hashes. > > > > Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8. > > > > Set up a 3-node cluster. > > > > Tested several flows. > > > > > > > > Thanks, > > > > Kotaro > > > > > > > > > > > > On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee > > > .invalid> > > > > wrote: > > > > > > > > > +1 (non-binding) > > > > > > > > > > Verified commit id, checksums, and signatures > > > > > Successfully built and ran tests on Linux with Java 1.8.0_252 and > Java > > > > > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS > > > > > Ran data flows on standalone and cluster > > > > > Verified JMS improvements, InvokeHTTP changes, and Azure > integration in > > > > > commercial and gov regions > > > > > > > > > > -joey > > > > > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows < > rob.fell...@gmail.com > > > > , > > > > > wrote: > > > > > > + 1 (non-binding) > > > > > > > > > > > > Ran through the release helper, verified checksums and sigs. > > > > > > Full build with java 11 > > > > > > Verified basic app usage/functionality. > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid > > > wrote: > > > > > > > > > > > > > +1 (non-binding) > > > > > > > Ran through the release helper. Deployed a 10 node cluster on > Azure > > > > and > > > > > > > verified the functionality of new ADLS processors with a > standard > > > > flow. > > > > > > > Looks good to me. > > > > > > > > > > > > > > Thanks, > > > > > > > Muazma > > > > > > > > > > > > > > On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim < > > > > > andrewlim.apa...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > > > > > -Ran full clean install on OS X (Catalina 10.15.2) > > > > > > > > -Tested secure NiFi with secure NiFi Registry 0.7.0 > > > > > > > > -Ran basic flows successfully; tested basic versioned flow > > > > > functionality > > > > > > > > -Reviewed documentation updates. Lots of a great additions in > > > this > > > > > > > release! > > > > > > > > -Reviewed core UI fixes and improvements. Verified that > > > controller > > > > > > > > services are searchable [1], but filed a Jira for the > navigation > > > to > > > > > the > > > > > > > > controller service being broken [2]. > > > > > > > > > > > > > > > > Drew > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-5925 < > > > > > > > > https://issues.apache.org/jira/browse/NIFI-5925> > > > > > > > > [2] https://issues.apache.org/jira/browse/NIFI-7742 < > > > > > > > > https://issues.apache.org/jira/browse/NIFI-7742> > > > > > > > > > > > > > > > > > On Aug 13, 2020, at 4:31 PM, Joe Witt > > > > wrote: > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > I am pleased to be calling this vote for the source > release of > > > > > Apache > > > > > > > > NiFi > > > > > > > > > 1.12.0. > > > > > > > > > > > > > > > > > > The source zip, including signatures, digests, etc. can be > > > found > > > > > at: > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1165 > > > > > > > > > > > > > > > > > > The source being voted upon and the convenience binaries > can be > > >
Re: Pull request for NIFI-1207
Hi Gavin, Can you rebase and squash your commits into one single commit for your pull request? (you may want to do it after 1.12.0 is released, which should happen today or tomorrow so that you can update the reference to 1.13.0-SNAPSHOT) Then there are a few things that should be changed: the processor should have the same version as what is in master and all the dependencies to NiFi should use what is available in master (currently 1.12.0-SNAPSHOT but soon 1.13.0-SNAPSHOT) Then I'd suggest ways for reviewers to test your pull request. Do you have any suggestions for Docker containers/images that could be used to test your pull request? Anything you can provide to help people will greatly increase the chances for a faster review. You may also want to have a look at the contributor guide [1]. Thanks, Pierre [1] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide Le mar. 18 août 2020 à 18:23, Gavin Leithall a écrit : > Hi, > > I raised a pull request for NIFI-1207 last week ( > https://github.com/apache/nifi/pull/4467). > > I confirmed most the of the PR checks (squashing commits being the most > notable exception) - is there anything you would like me to do before it > can be reviewed? > > Best regards, > Gavin > This electronic message contains information from CACI International Inc or > subsidiary companies, which may be confidential, proprietary, > privileged or otherwise protected from disclosure. The information is > intended to be used solely by the recipient(s) named above. If you are not > an intended recipient, be aware that any review, disclosure, copying, > distribution or use of this transmission or its contents is prohibited. If > you have received this transmission in error, please notify us immediately > at postmas...@caci.co.uk > Viruses: Although we have taken steps to ensure that this e-mail and > attachments are free from any virus, we advise that in keeping with good > computing practice the recipient should ensure they are actually virus > free. > > CACI Limited. Registered in England & Wales. Registration No. 1649776. > CACI House, Avonmore Road, London, W14 8TS >
Re: info on nifi clustering and persisting the flow and flow file data of the repositories
> > > Hi Nifi, > > I am a java developer, working on a Nifi cluster set up. We have > configured 3 nodes in the nifi cluster along with a single instance of > Zookeeper. This whole setup is containerized. > > For customizing the nifi properties, we have created new image nifi > binaries and modifying the appropriate property file. > > 1) My question is if we configure nifi in cluster mode to use zookeeper, > is it enough for taking the back of the flow and the other repositories. Is > there any specific step or config required to back up the above. > 2) We want to use the provenance repository as a way of checking the > current status of the Nifi and as well as archive it for later analysis. So > other than nifi itself is there any other tool to view this data. > > I have found in some stacktrace that we have to manually take backup of > the config folder and the repositories in order for a nifi node to recover > or for any other new node to read and process where the previous pod left, > in case of some error and the previous pod stopped working. If so then what > is the use of configuring zookeeper. > > -- > Thanks & Regards, > Krishna. > -- -- Thanks & Regards, Krishna.
Suggestions for splitting, then reassembling documents
I am writing custom processors that juggle medical documents (in a more or less proprietary format). The document are always XML and contain two, major parts: 1. an original document which may be text, HL7v2 or XML and may contain HTML between ... , could be many megabytes in size 2. XML structure representing data extracted from (a) in myriad XML elements, rarely more than a few hundred kilobytes in size I am using XStreamto serialize #2 after I've parsed it into POJOs for later use. It's too over the top to base-64 encode #1 to survive serialization by XStreamand it buys me nothing except the convenience of making #1 conceptually identical to #2. Since I don't need to dig down into #1 or analyze it, and it's so big, processing it at all is costly and undesirable. What I thought I'd investigate is the possibility of splitting ... (#1) into a separate flowfile to be reassembled by a later processor, but with (literally) millions of these files flowing through NiFi, I wonder about the advisability of splitting them up then hoping I can unite the correct parts and how to accomplish that (discrete attribute ids on constituent parts?). The reassembly would involve deserializing #2, working with that data to generate a new document (HL7v4/FHIR, other formats) along with reinserting #1. Yes, I have examined /SplitXml/ and /SplitContent/, but I need to do much more than just split the flowfile at the time I have it in my hands, hence, a custom processor. Similarly, /MergeContent/ will not be helpful for reassembly. So, specifically, I can easily generate a flowfile attribute, an id that discretely identifies these two now separate documents as suitable to weld back together. However, I have not yet experimented with flowfiles randomly (?) showing up together later in the flow within easy reach of one processor for reassembly. Obviously, /Split/- and /MergeContent/ must be in the habit of dealing with this situation, but I have no experience with them outside my primitive imagination. I'm asking for suggestions, best practice, gotchas, warnings or any other thoughts. Russ
Pull request for NIFI-1207
Hi, I raised a pull request for NIFI-1207 last week (https://github.com/apache/nifi/pull/4467). I confirmed most the of the PR checks (squashing commits being the most notable exception) - is there anything you would like me to do before it can be reviewed? Best regards, Gavin This electronic message contains information from CACI International Inc or subsidiary companies, which may be confidential, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named above. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify us immediately at postmas...@caci.co.uk Viruses: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. CACI Limited. Registered in England & Wales. Registration No. 1649776. CACI House, Avonmore Road, London, W14 8TS
