Re: [discuss] Apache NiFi 1.11.0
There's an open PR [1] for NIFI-6852. Could really use this in 1.11.0. [1] https://github.com/apache/nifi/pull/3973 On Mon, Jan 6, 2020 at 12:06 PM Joe Witt wrote: > Team, > > We've already seen a good stream of nice fixes, improvements, and some > minor features land on NIFi 1.11.0. It is enough to my eyes to warrant > doing a release to pull these in plus it helps get back our release cadence > mojo. > > I'll volunteer to RM this one as well as it almost makes me feel like a > software developer still. > > Here are things already resolved for 1.11 > > https://issues.apache.org/jira/browse/NIFI-6956?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.11.0 > > Here are things open but tagged to 1.11 > > https://issues.apache.org/jira/browse/NIFI-6982?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.11.0 > > I'l start cleaning/moving as necessary. Please advise if there are major > things not present that we need to consider. But otherwise lets keep the > ball moving forward and get after more regular releases again. > > Thanks > Joe >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)
Looks like I missed the vote by a smidge, but I did work through the helper guide on mxlinux 18 with no issues. So, I'll cast a post-vote +1! On Sat, Jan 11, 2020 at 12:33 PM Arpad Boda wrote: > Apache NiFi Community, > > I am pleased to announce that the 0.7.0 release of Apache NiFi MiNiFi > C++ passes with > 5 +1 (binding) votes > 2 +1 (non-binding) votes > 0 0 votes > 0 -1 votes > > Thanks to all who helped make this release possible. > > Here is the PMC vote thread: > > http://apache-nifi.1125220.n5.nabble.com/VOTE-Release-Apache-NiFi-MiNiFi-C-0-7-0-RC1-td29724.html > > On Sat, Jan 11, 2020 at 6:30 PM Arpad Boda wrote: > > > +1 - verified build, checksums and execution on Debian. > > > > Thanks all for the documentation improvements, will adjust helper and > > readme accordingly! > > > > On Sat, Jan 11, 2020 at 3:57 AM Andy LoPresto > > wrote: > > > >> +1 (binding) > >> > >> I encountered a number of obstacles during this validation, some of > which > >> are definitely because I haven’t worked on the C++ effort (or even built > >> it) in at least 6 months. These are not complaints, just wrinkles I > >> captured so we can improve this process for next time. Noted here for > >> posterity: > >> > >> * The SHA-512 digest I calculated locally matched the email, but the > >> .sha512 files are not published in the hosted server for any artifacts. > >> * The GPG verification command in the helper email should include -v to > >> show the underlying digest algorithm used > >> * The wget commands have newlines inserted, which means they cannot be > >> copied/pasted into the terminal without manual modification > >> * The README section on bootstrapping helped immensely, but is not > >> perfectly aligned with the current process > >> * The wording of “disable tests…..disabled” is unclear (in this case it > >> means that the tests will be run) > >> * The bootstrap instructions are missing the directive to change into > the > >> build/ directory before running make (directory in example prompt is > wrong) > >> * The bootstrap instructions are missing the directive to untar the > >> binary artifact and change into that directory before running > >> ./bin/minifi.sh start > >> * A sample flow (config.yml) with a GenerateFlowFile and LogAtttribute > >> flow would be helpful to allow people to verify the successful install > of > >> MiNiFi without going through the full flow design in NiFi, export > template, > >> convert template process > >> > >> All in all, a lot of great work done on this release. Thanks Arpad. > >> > >> > >> Andy LoPresto > >> alopre...@apache.org > >> alopresto.apa...@gmail.com > >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > >> > >> > On Jan 10, 2020, at 12:55 PM, Matt Gilman > >> wrote: > >> > > >> > +1 (binding) > >> > > >> > Ran through release helper. Verified signature, checksums, build, > tests, > >> > etc. Looks good. > >> > > >> > Thanks for RMing Arpad! > >> > > >> > On Fri, Jan 10, 2020 at 3:39 PM Kevin Doran > >> wrote: > >> > > >> >> +1 (binding) > >> >> > >> >> Ran through the steps in the release helper guide. Noticed a few > >> >> release helper instructions that can be improved for next time (no > >> >> mention of bootstrap.sh), > >> >> but was able to figure it out by using the README file included in > the > >> >> source release. > >> >> > >> >> Hashes & sig all looked good. Was able to build, including the docker > >> >> image. Tests > >> >> all passed. Tested integration with a NiFi cluster with the 0.7.0 > >> >> minifi sending flow files over s2s and everything worked as expected. > >> >> > >> >> Overall, seems to be a very solid, polished release. Nice work all! > >> >> > >> >> On Fri, Jan 10, 2020 at 3:35 PM Joe Witt wrote: > >> >>> > >> >>> +1 (binding) > >> >>> > >> >>> Comments > >> >>> - Notice file copyright year needs to be 2020 > >> >>> - I did not enable python support but I get the minifi-python dir > >> anyway > >> >>> and log entry on startup such as > >> >>> Caught Exception ModuleNotFoundError: No module named 'google' > >> >>> > >> >>> Great progress with this release! Nice work. Building and running > >> tests > >> >>> was easier than I ever remember. > >> >>> > >> >>> Thanks > >> >>> > >> >>> On Fri, Jan 10, 2020 at 8:27 AM Dániel Bakai < > bakaid.apa...@gmail.com > >> > > >> >>> wrote: > >> >>> > >> +1, non-binding > >> > >> Verifications performed: > >> > >> SHA256 checksums downloaded: OK > >> SHA512 checksum of nifi-minifi-cpp-0.7.0-source.tar.gz sent in > mail: > >> OK > >> GPG signatures downloaded: OK > >> Git tag in email matches sources in > >> >> nifi-minifi-cpp-0.7.0-source.tar.gz: OK > >> > >> bootstrap.sh with default options && make && make package && sudo > >> make > >> >> test > >> ARGS="-j4 --output-on-failure" && run package with a > GenerateFlowFile > >> >> -> > >> LogAttribute flow: > >> macOS 10.14.6: TailFileTests
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)
Apache NiFi Community, I am pleased to announce that the 0.7.0 release of Apache NiFi MiNiFi C++ passes with 5 +1 (binding) votes 2 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread: http://apache-nifi.1125220.n5.nabble.com/VOTE-Release-Apache-NiFi-MiNiFi-C-0-7-0-RC1-td29724.html On Sat, Jan 11, 2020 at 6:30 PM Arpad Boda wrote: > +1 - verified build, checksums and execution on Debian. > > Thanks all for the documentation improvements, will adjust helper and > readme accordingly! > > On Sat, Jan 11, 2020 at 3:57 AM Andy LoPresto > wrote: > >> +1 (binding) >> >> I encountered a number of obstacles during this validation, some of which >> are definitely because I haven’t worked on the C++ effort (or even built >> it) in at least 6 months. These are not complaints, just wrinkles I >> captured so we can improve this process for next time. Noted here for >> posterity: >> >> * The SHA-512 digest I calculated locally matched the email, but the >> .sha512 files are not published in the hosted server for any artifacts. >> * The GPG verification command in the helper email should include -v to >> show the underlying digest algorithm used >> * The wget commands have newlines inserted, which means they cannot be >> copied/pasted into the terminal without manual modification >> * The README section on bootstrapping helped immensely, but is not >> perfectly aligned with the current process >> * The wording of “disable tests…..disabled” is unclear (in this case it >> means that the tests will be run) >> * The bootstrap instructions are missing the directive to change into the >> build/ directory before running make (directory in example prompt is wrong) >> * The bootstrap instructions are missing the directive to untar the >> binary artifact and change into that directory before running >> ./bin/minifi.sh start >> * A sample flow (config.yml) with a GenerateFlowFile and LogAtttribute >> flow would be helpful to allow people to verify the successful install of >> MiNiFi without going through the full flow design in NiFi, export template, >> convert template process >> >> All in all, a lot of great work done on this release. Thanks Arpad. >> >> >> Andy LoPresto >> alopre...@apache.org >> alopresto.apa...@gmail.com >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >> >> > On Jan 10, 2020, at 12:55 PM, Matt Gilman >> wrote: >> > >> > +1 (binding) >> > >> > Ran through release helper. Verified signature, checksums, build, tests, >> > etc. Looks good. >> > >> > Thanks for RMing Arpad! >> > >> > On Fri, Jan 10, 2020 at 3:39 PM Kevin Doran >> wrote: >> > >> >> +1 (binding) >> >> >> >> Ran through the steps in the release helper guide. Noticed a few >> >> release helper instructions that can be improved for next time (no >> >> mention of bootstrap.sh), >> >> but was able to figure it out by using the README file included in the >> >> source release. >> >> >> >> Hashes & sig all looked good. Was able to build, including the docker >> >> image. Tests >> >> all passed. Tested integration with a NiFi cluster with the 0.7.0 >> >> minifi sending flow files over s2s and everything worked as expected. >> >> >> >> Overall, seems to be a very solid, polished release. Nice work all! >> >> >> >> On Fri, Jan 10, 2020 at 3:35 PM Joe Witt wrote: >> >>> >> >>> +1 (binding) >> >>> >> >>> Comments >> >>> - Notice file copyright year needs to be 2020 >> >>> - I did not enable python support but I get the minifi-python dir >> anyway >> >>> and log entry on startup such as >> >>> Caught Exception ModuleNotFoundError: No module named 'google' >> >>> >> >>> Great progress with this release! Nice work. Building and running >> tests >> >>> was easier than I ever remember. >> >>> >> >>> Thanks >> >>> >> >>> On Fri, Jan 10, 2020 at 8:27 AM Dániel Bakai > > >> >>> wrote: >> >>> >> +1, non-binding >> >> Verifications performed: >> >> SHA256 checksums downloaded: OK >> SHA512 checksum of nifi-minifi-cpp-0.7.0-source.tar.gz sent in mail: >> OK >> GPG signatures downloaded: OK >> Git tag in email matches sources in >> >> nifi-minifi-cpp-0.7.0-source.tar.gz: OK >> >> bootstrap.sh with default options && make && make package && sudo >> make >> >> test >> ARGS="-j4 --output-on-failure" && run package with a GenerateFlowFile >> >> -> >> LogAttribute flow: >> macOS 10.14.6: TailFileTests sometimes fail, otherwise OK >> ubuntu:bionic docker container: had to install 'tzdata' package for >> ExpressionLanguageTest to work, CTailFileChunkTests and >> CTailFileDelimitedTests consistently fail when ran in parallel, >> running >> them sequentially works, otherwise OK >> centos:7 docker container: had to install 'zlib-devel' and 'which', >> otherwise OK >> debian:stretch docker container: OK >> fedora:29 docker container: had to install
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)
+1 - verified build, checksums and execution on Debian. Thanks all for the documentation improvements, will adjust helper and readme accordingly! On Sat, Jan 11, 2020 at 3:57 AM Andy LoPresto wrote: > +1 (binding) > > I encountered a number of obstacles during this validation, some of which > are definitely because I haven’t worked on the C++ effort (or even built > it) in at least 6 months. These are not complaints, just wrinkles I > captured so we can improve this process for next time. Noted here for > posterity: > > * The SHA-512 digest I calculated locally matched the email, but the > .sha512 files are not published in the hosted server for any artifacts. > * The GPG verification command in the helper email should include -v to > show the underlying digest algorithm used > * The wget commands have newlines inserted, which means they cannot be > copied/pasted into the terminal without manual modification > * The README section on bootstrapping helped immensely, but is not > perfectly aligned with the current process > * The wording of “disable tests…..disabled” is unclear (in this case it > means that the tests will be run) > * The bootstrap instructions are missing the directive to change into the > build/ directory before running make (directory in example prompt is wrong) > * The bootstrap instructions are missing the directive to untar the binary > artifact and change into that directory before running ./bin/minifi.sh start > * A sample flow (config.yml) with a GenerateFlowFile and LogAtttribute > flow would be helpful to allow people to verify the successful install of > MiNiFi without going through the full flow design in NiFi, export template, > convert template process > > All in all, a lot of great work done on this release. Thanks Arpad. > > > Andy LoPresto > alopre...@apache.org > alopresto.apa...@gmail.com > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > On Jan 10, 2020, at 12:55 PM, Matt Gilman > wrote: > > > > +1 (binding) > > > > Ran through release helper. Verified signature, checksums, build, tests, > > etc. Looks good. > > > > Thanks for RMing Arpad! > > > > On Fri, Jan 10, 2020 at 3:39 PM Kevin Doran > wrote: > > > >> +1 (binding) > >> > >> Ran through the steps in the release helper guide. Noticed a few > >> release helper instructions that can be improved for next time (no > >> mention of bootstrap.sh), > >> but was able to figure it out by using the README file included in the > >> source release. > >> > >> Hashes & sig all looked good. Was able to build, including the docker > >> image. Tests > >> all passed. Tested integration with a NiFi cluster with the 0.7.0 > >> minifi sending flow files over s2s and everything worked as expected. > >> > >> Overall, seems to be a very solid, polished release. Nice work all! > >> > >> On Fri, Jan 10, 2020 at 3:35 PM Joe Witt wrote: > >>> > >>> +1 (binding) > >>> > >>> Comments > >>> - Notice file copyright year needs to be 2020 > >>> - I did not enable python support but I get the minifi-python dir > anyway > >>> and log entry on startup such as > >>> Caught Exception ModuleNotFoundError: No module named 'google' > >>> > >>> Great progress with this release! Nice work. Building and running > tests > >>> was easier than I ever remember. > >>> > >>> Thanks > >>> > >>> On Fri, Jan 10, 2020 at 8:27 AM Dániel Bakai > >>> wrote: > >>> > +1, non-binding > > Verifications performed: > > SHA256 checksums downloaded: OK > SHA512 checksum of nifi-minifi-cpp-0.7.0-source.tar.gz sent in mail: > OK > GPG signatures downloaded: OK > Git tag in email matches sources in > >> nifi-minifi-cpp-0.7.0-source.tar.gz: OK > > bootstrap.sh with default options && make && make package && sudo make > >> test > ARGS="-j4 --output-on-failure" && run package with a GenerateFlowFile > >> -> > LogAttribute flow: > macOS 10.14.6: TailFileTests sometimes fail, otherwise OK > ubuntu:bionic docker container: had to install 'tzdata' package for > ExpressionLanguageTest to work, CTailFileChunkTests and > CTailFileDelimitedTests consistently fail when ran in parallel, > running > them sequentially works, otherwise OK > centos:7 docker container: had to install 'zlib-devel' and 'which', > otherwise OK > debian:stretch docker container: OK > fedora:29 docker container: had to install 'zlib-devel' and 'which', > otherwise OK > ubuntu:xenial docker container: had to install 'tzdata' package for > ExpressionLanguageTest to work, otherwise OK > > Run appropriate convenience binary with a GenerateFlowFile -> > >> LogAttribute > flow: > macOS 10.14.6: OK > ubuntu:bionic docker container: OK > centos:7 docker container: OK > debian:stretch docker container: OK > fedora:29 docker container: OK > ubuntu:xenial docker container: OK > General note: there is a dynamic libpython dependency
