[ANNOUNCE] Apache NiFi MiNiFi C++ 0.99.0 release
Hello The Apache NiFi team would like to announce the release of Apache NiFi MiNiFi C++ 0.99.0. New features in this release: Added support for using NiFi 2.0 Python processors in MiNiFi C++ Added new python based multiplatform bootstrap script Added encryption support for sensitive properties in flow configuration Releasing Windows installer now can be done (and will be done) under the Apache license Added support for service installation on MacOS Added C2 debug command to MiNiFi Controller Added support for setting MiNiFi properties from command line Added system load average field to C2 and Prometheus metrics Added support for manually configuring RocksDB options Added custom delimiter property for ListenTCP processor Added bandwidth limit properties to InvokeHTTP processor Added JSON flow configuration examples New processors: Added PutSmb, FetchSmb and ListSmb processor for SMB networking protocol support Added PushGrafanaLokiGrpc and PushGrafanaLokiREST processors for pushing logs to Grafana Loki Added JoltTransform to use Jolt JSON transformations Added SplitText processor Added AttributeRollingWindow processor Changes and improvements: Dropped support for disabling peer verification in InvokeHTTP Corrupt flow files are now filtered to avoid errors in the flow Using administrative yield duration instead of onschedule retry interval in scheduling adjusting to NiFi's functionality Fixed high disk IO usage issue with MergeContent Fixed the site-to-site transfer or large files Fixed memory leak caused by unused loggers Fixed yielding processors to still respect scheduling period Upgraded dependencies: Upgraded OpenSSL to version 3.3.0 Upgraded AWS SDK to version 1.11.219 with support for new AWS regions Upgraded libuvc to version 0.0.7 Upgraded docker base image to alpine:3.18 Upgraded Sol2 to version 3.3.0 MiNiFi—a subproject of Apache NiFi—is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation. Specific goals for the initial thrust of the MiNiFi effort comprise: Small size and low resource consumption Central management of agents Generation of data provenance (full chain of custody of information) Integration with NiFi for follow-on dataflow management More details on Apache NiFi MiNiFi can be found here: https://nifi.apache.org/minifi The release artifacts can be downloaded from here: https://nifi.apache.org/download/ Issues closed/resolved for this list can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.0 Thank you The Apache NiFi team
[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.99.0
Apache NiFi Community, I am pleased to announce that the 0.99.0 release of Apache NiFi MiNiFi C++ passes with 3 +1 (binding) votes 3 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the PMC vote thread: https://lists.apache.org/thread/ox6bg1l278yqwcp2htwmrs1y3jw1jmzs Thanks, Gabor
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - Verified hashes and signatures - Successfully built NiFi 2.0.0-M3 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-35-generic - java 21 2023-09-19 LTS - Apache Maven 3.9.6 - Designed and ran a simple flow with S3 upload - Tested python extension using a flow with PromptChatGPT processor - Tested S2S communication and HTTP data forwarding from MiNiFi C++ Thanks David for RMing! Regards, Gabor On Thu, 16 May 2024 at 13:12, Marton Szasz wrote: > +1 (binding) > > Followed the usual steps, compiled and tested NiFi in this environment > (Ubuntu 24.04): > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /home/szaszm/apache-maven-3.9.6 > Java version: 21.0.3, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-21-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "6.8.0-31-generic", arch: "amd64", family: > "unix" > > Tested receiving logs from minifi c++ through HTTP, and decompressing them. > > Thanks for the release, David! > > Marton > > On 5/16/24 11:09 AM, Márk Báthori wrote: > > +1 (non-binding) > > > > - went through the helper guide, > > - did a full build with contrib check > > - verified signatures and hashes > > > > Environment: > > - macOS Version 14.3.1 > > - OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35) > > - Apache Maven 3.9.6 > > > > Created and ran some simple flows. > > > > Thanks for RMing David! > > > > Regards, > > Mark > > > > Krisztina Zsihovszki ezt írta (időpont: 2024. máj. > > 16., Cs, 10:40): > > > >> +1 (non-binding) > >> > >> - Verified signatures and hashes > >> - Ran build using Maven 3.9.5 on macOS 13.5 with Java 21-zulu (build > 21+35) > >> - Contrib check, unit tests passed > >> > >> Verified these tickets: > >> > >> [NIFI-13146] - ConsumeSlack processor rate limited > >> [NIFI-12732] - ListS3 should reset its tracking state after > configuration > >> change > >> > >> Thanks for RMing, David! > >> > >> On Thu, May 16, 2024 at 9:27 AM Ferenc Kis > >> wrote: > >> > >>> +1 (non-binding) > >>> > >>> Went through the helper guide, local maven repo cleaned up, full clean > >>> build with contrib check, verified signatures and hashes > >>> > >>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > >>> Maven home: /Users/fkis/.sdkman/candidates/maven/current > >>> Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: > >>> > /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home > >>> Default locale: en_HU, platform encoding: UTF-8 > >>> OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac" > >>> > >>> Validations performed: > >>> - Started NiFi, created a simple flow with ListenHTTP and Input Port. > >>> Validated ListenHTTP processor is able to receive data > >>> - Started MiNiFi Java: > >>>* created a simple GenerateFlowFile -> InvokeHttp flow and > >>> GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > >>> protocol > >>>* Validated that connectivity between NiFi and MiNiFi works via both > >>> InvokeHTTP and S2S > >>> - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > >>> MiNiFi-2.0.0-M2 > >>> - NIFI-13123 [MiNiFi] Async C2 Operation Queue > >>> > >>> Thanks for RMing David! > >>> > >>> Regards > >>> Ferenc > >>> > >>> On Thu, May 16, 2024 at 3:44 AM Csaba Bejan > >> wrote: > +1 (binding) > > - Went through the helper guide and did a clean build > - Verified signatures and hashes > - Built on OSX 14.2.1 > - Java version: Zulu21.28+85-CA (build 21+35) > - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > - Started NiFi and created a simple flow > - Started MiNiFi and verified integration with C2 Server. Played > >>> around > with the C2 protocol (Operations - Update, Transfer, Describe...) > > Verified: > > - NIFI-13123 [MiNiFi] Async C2 Operation Queue > - NIFI-13019 ClassNotFoundException when using HandleHttpRequest > in > MiNiFi-2.0.0-M2 > > Thanks for RMing, David! > > Regards, > Csaba > > On Mon, May 13, 2024 at 11:49 PM 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-M3. > > > > 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 and the convenience binaries are available > > on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > >>
[VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.99.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ The Git tag is minifi-cpp-0.99.0-RC4 The Git commit ID is 2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: SHA256: d6982ad6343d42c57c63e7503bb3ba55ddeb1f1cdbbd31064018ec06148b4b3b SHA512: 333f284cd546501612c695ce0dd288ca35fa0bc0ae5a905d4fb54e9494b51fc76e5d4d7de387f07d9ac8be158f022975c5cf487a6e19f12ac6020c4d60f58ab2 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 124 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Thanks Joe! Then it's probably the same build issue we found with this version. Regards, Gabor On Wed, 8 May 2024 at 21:32, Joe Witt wrote: > pkgutil --pkg-info=com.apple.pkg.CLTools_Executables > package-id: com.apple.pkg.CLTools_Executables > version: 15.3.0.0.1.1708646388 > volume: / > location: / > install-time: 1710790868 > sw_vers > ProductName: macOS > ProductVersion: 14.4.1 > BuildVersion: 23E224 > > Thanks > Joe > > > On Wed, May 8, 2024 at 8:15 AM Gábor Gyimesi wrote: > > > For checking the xcode version you can use the following command: > > $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables > > And to check the macos version use the following command: > > $ sw_vers > > > > On Wed, 8 May 2024 at 16:35, Gábor Gyimesi wrote: > > > > > The build output should be visible on the stdout and stderr channels so > > > the output should be visible above the python output. If it is hidden > for > > > some reason when you use the python bootstrap, you could use the cmake > > > commands to rerun the build with the default extensions: > > > $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . > > --target > > > package > > > > > > BR, > > > Gabor > > > > > > On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > > > > > >> Gabor - thanks. Can you share a specific command and/or file I can > look > > >> at > > >> which would have the good info? > > >> > > >> On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi > > >> wrote: > > >> > > >> > Hi Team, > > >> > > > >> > In light of the issues found on the MacOS platform I am canceling > RC3 > > >> and > > >> > will create RC4 once the issues are resolved. > > >> > > > >> > Two of the runtime issues have already been addressed by these 2 > PRs: > > >> > https://github.com/apache/nifi-minifi-cpp/pull/1782 > > >> > https://github.com/apache/nifi-minifi-cpp/pull/1783 > > >> > > > >> > The investigation of the build issues on the latest MacOS version is > > >> still > > >> > ongoing. > > >> > > > >> > @Joe can you confirm that your build issue is on the MacOS version > > >> 14.4.1 > > >> > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > > >> > Otherwise please share the issue so we could check that one out as > > well. > > >> > > > >> > Thanks, > > >> > Gabor > > >> > > > >> > On Wed, 8 May 2024 at 15:40, Adam Debreceni > > >> wrote: > > >> > > > >> > > -1 (non-binding) > > >> > > > > >> > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode > 15.1 > > >> and > > >> > > deployed simple flow through c2 protocol, > > >> > > but I have found the following on macos: > > >> > > - getting errors running nifi python processors, due to python > > >> > searching > > >> > > for minifi_native.so > > >> > > - minifi.plist is missing from the package making it impossible > to > > >> > > install the agent as a service > > >> > > > > >> > > (We also have to be mindful about the flex package as either we > use > > >> the > > >> > > system flex or the brew flex > > >> > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be > > set > > >> > > accordingly) > > >> > > > > >> > > We also found that it does not compile on the newest macos 14.4.1 > > with > > >> > > xcode 15.3. > > >> > > > > >> > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > > > >> > wrote: > > >> > > > > >> > > > +1 (non-binding) > > >> > > > > > >> > > > -Verified signature, hashes and git commit hash > > >> > > > -Built it from source with default extensions on RockyLinux 9 > > >> (aarch64 > > >> > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the > > new > > >> > > > python based bootstrap > > >> > > > -Ran through a couple of C2 initiated flows > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
For checking the xcode version you can use the following command: $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables And to check the macos version use the following command: $ sw_vers On Wed, 8 May 2024 at 16:35, Gábor Gyimesi wrote: > The build output should be visible on the stdout and stderr channels so > the output should be visible above the python output. If it is hidden for > some reason when you use the python bootstrap, you could use the cmake > commands to rerun the build with the default extensions: > $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . --target > package > > BR, > Gabor > > On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > >> Gabor - thanks. Can you share a specific command and/or file I can look >> at >> which would have the good info? >> >> On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi >> wrote: >> >> > Hi Team, >> > >> > In light of the issues found on the MacOS platform I am canceling RC3 >> and >> > will create RC4 once the issues are resolved. >> > >> > Two of the runtime issues have already been addressed by these 2 PRs: >> > https://github.com/apache/nifi-minifi-cpp/pull/1782 >> > https://github.com/apache/nifi-minifi-cpp/pull/1783 >> > >> > The investigation of the build issues on the latest MacOS version is >> still >> > ongoing. >> > >> > @Joe can you confirm that your build issue is on the MacOS version >> 14.4.1 >> > with xcode 15.3 or that it is due to the flex issue Adam mentioned? >> > Otherwise please share the issue so we could check that one out as well. >> > >> > Thanks, >> > Gabor >> > >> > On Wed, 8 May 2024 at 15:40, Adam Debreceni >> wrote: >> > >> > > -1 (non-binding) >> > > >> > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 >> and >> > > deployed simple flow through c2 protocol, >> > > but I have found the following on macos: >> > > - getting errors running nifi python processors, due to python >> > searching >> > > for minifi_native.so >> > > - minifi.plist is missing from the package making it impossible to >> > > install the agent as a service >> > > >> > > (We also have to be mindful about the flex package as either we use >> the >> > > system flex or the brew flex >> > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set >> > > accordingly) >> > > >> > > We also found that it does not compile on the newest macos 14.4.1 with >> > > xcode 15.3. >> > > >> > > On Wed, May 8, 2024 at 1:15 PM Martin Zink >> > wrote: >> > > >> > > > +1 (non-binding) >> > > > >> > > > -Verified signature, hashes and git commit hash >> > > > -Built it from source with default extensions on RockyLinux 9 >> (aarch64 >> > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new >> > > > python based bootstrap >> > > > -Ran through a couple of C2 initiated flows >> > > > >> > > > Everything worked as expected, >> > > > >> > > > >> > > > thanks Gabor for RMing great work, >> > > > Martin >> > > > >> > > > >> > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi >> > > wrote: >> > > > > >> > > > > Hi Joe, >> > > > > >> > > > > Could you check the ninja output for the build error? The output >> you >> > > sent >> > > > > is only the bootstrap script's traceback of the build step's >> failure, >> > > but >> > > > > there should probably be an error in the build output as well >> > starting >> > > > with >> > > > > "error: ". >> > > > > >> > > > > BR, >> > > > > Gabor >> > > > > >> > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: >> > > > > >> > > > > > Hello >> > > > > > >> > > > > > Sigs/Hashes are good. >> > > > > > >> > > > > > Building source on macos I'm getting a build failure. The only >> > > option >> &
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
The build output should be visible on the stdout and stderr channels so the output should be visible above the python output. If it is hidden for some reason when you use the python bootstrap, you could use the cmake commands to rerun the build with the default extensions: $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . --target package BR, Gabor On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > Gabor - thanks. Can you share a specific command and/or file I can look at > which would have the good info? > > On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi wrote: > > > Hi Team, > > > > In light of the issues found on the MacOS platform I am canceling RC3 and > > will create RC4 once the issues are resolved. > > > > Two of the runtime issues have already been addressed by these 2 PRs: > > https://github.com/apache/nifi-minifi-cpp/pull/1782 > > https://github.com/apache/nifi-minifi-cpp/pull/1783 > > > > The investigation of the build issues on the latest MacOS version is > still > > ongoing. > > > > @Joe can you confirm that your build issue is on the MacOS version 14.4.1 > > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > > Otherwise please share the issue so we could check that one out as well. > > > > Thanks, > > Gabor > > > > On Wed, 8 May 2024 at 15:40, Adam Debreceni > wrote: > > > > > -1 (non-binding) > > > > > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 > and > > > deployed simple flow through c2 protocol, > > > but I have found the following on macos: > > > - getting errors running nifi python processors, due to python > > searching > > > for minifi_native.so > > > - minifi.plist is missing from the package making it impossible to > > > install the agent as a service > > > > > > (We also have to be mindful about the flex package as either we use the > > > system flex or the brew flex > > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set > > > accordingly) > > > > > > We also found that it does not compile on the newest macos 14.4.1 with > > > xcode 15.3. > > > > > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > -Verified signature, hashes and git commit hash > > > > -Built it from source with default extensions on RockyLinux 9 > (aarch64 > > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > > > > python based bootstrap > > > > -Ran through a couple of C2 initiated flows > > > > > > > > Everything worked as expected, > > > > > > > > > > > > thanks Gabor for RMing great work, > > > > Martin > > > > > > > > > > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi > > > wrote: > > > > > > > > > > Hi Joe, > > > > > > > > > > Could you check the ninja output for the build error? The output > you > > > sent > > > > > is only the bootstrap script's traceback of the build step's > failure, > > > but > > > > > there should probably be an error in the build output as well > > starting > > > > with > > > > > "error: ". > > > > > > > > > > BR, > > > > > Gabor > > > > > > > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > > > > > > > Hello > > > > > > > > > > > > Sigs/Hashes are good. > > > > > > > > > > > > Building source on macos I'm getting a build failure. The only > > > option > > > > > > selected was to skip tests otherwise left as defaults. Am > > following > > > > the > > > > > > readme and release guide. > > > > > > > > > > > > ninja: build stopped: subcommand failed. > > > > > > Build was unsuccessful > > > > > > Traceback (most recent call last): > > > > > > File > > > > > > > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > > > > line 62, in > > > > > > main_menu(minifi_options
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Hi Team, In light of the issues found on the MacOS platform I am canceling RC3 and will create RC4 once the issues are resolved. Two of the runtime issues have already been addressed by these 2 PRs: https://github.com/apache/nifi-minifi-cpp/pull/1782 https://github.com/apache/nifi-minifi-cpp/pull/1783 The investigation of the build issues on the latest MacOS version is still ongoing. @Joe can you confirm that your build issue is on the MacOS version 14.4.1 with xcode 15.3 or that it is due to the flex issue Adam mentioned? Otherwise please share the issue so we could check that one out as well. Thanks, Gabor On Wed, 8 May 2024 at 15:40, Adam Debreceni wrote: > -1 (non-binding) > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 and > deployed simple flow through c2 protocol, > but I have found the following on macos: > - getting errors running nifi python processors, due to python searching > for minifi_native.so > - minifi.plist is missing from the package making it impossible to > install the agent as a service > > (We also have to be mindful about the flex package as either we use the > system flex or the brew flex > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set > accordingly) > > We also found that it does not compile on the newest macos 14.4.1 with > xcode 15.3. > > On Wed, May 8, 2024 at 1:15 PM Martin Zink wrote: > > > +1 (non-binding) > > > > -Verified signature, hashes and git commit hash > > -Built it from source with default extensions on RockyLinux 9 (aarch64 > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > > python based bootstrap > > -Ran through a couple of C2 initiated flows > > > > Everything worked as expected, > > > > > > thanks Gabor for RMing great work, > > Martin > > > > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi > wrote: > > > > > > Hi Joe, > > > > > > Could you check the ninja output for the build error? The output you > sent > > > is only the bootstrap script's traceback of the build step's failure, > but > > > there should probably be an error in the build output as well starting > > with > > > "error: ". > > > > > > BR, > > > Gabor > > > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > > > Hello > > > > > > > > Sigs/Hashes are good. > > > > > > > > Building source on macos I'm getting a build failure. The only > option > > > > selected was to skip tests otherwise left as defaults. Am following > > the > > > > readme and release guide. > > > > > > > > ninja: build stopped: subcommand failed. > > > > Build was unsuccessful > > > > Traceback (most recent call last): > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > > line 62, in > > > > main_menu(minifi_options, package_manager) > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > line 87, in main_menu > > > > done = > > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > > > package_manager) > > > > > > > > > > > > > > > > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > line 60, in do_one_click_build > > > > assert do_build(minifi_options, package_manager) > > > > > > > > > > > > So then I select to not use ninja and run the one click build again. > > > > It seems to run for much longer then the same output prints again. > > > > > > > > Thanks > > > > Joe > > > > > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > Built on ubuntu, verified signature and checksums. All tests > passed, > > > > > started and ran a simple flow with no issues. > > > > > > > > > > Nice job, team! > > > > &g
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Hi Joe, Could you check the ninja output for the build error? The output you sent is only the bootstrap script's traceback of the build step's failure, but there should probably be an error in the build output as well starting with "error: ". BR, Gabor On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > Hello > > Sigs/Hashes are good. > > Building source on macos I'm getting a build failure. The only option > selected was to skip tests otherwise left as defaults. Am following the > readme and release guide. > > ninja: build stopped: subcommand failed. > Build was unsuccessful > Traceback (most recent call last): > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > line 62, in > main_menu(minifi_options, package_manager) > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > line 87, in main_menu > done = main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > package_manager) > > > > > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > line 60, in do_one_click_build > assert do_build(minifi_options, package_manager) > > > So then I select to not use ninja and run the one click build again. > It seems to run for much longer then the same output prints again. > > Thanks > Joe > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > +1 (binding) > > > > Built on ubuntu, verified signature and checksums. All tests passed, > > started and ran a simple flow with no issues. > > > > Nice job, team! > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi > > wrote: > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > MiNiFi C++ 0.99.0. > > > > > > The source tarball, some binary builds, plus signatures and digests can > > be > > > found at: > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > > SHA256: > c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 > > > SHA512: > > > > > > > > > d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/lordgamez.asc > > > > > > A helpful reminder on how the release candidate verification process > > works: > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 121 issues were closed/resolved for this release: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 > > > > > > Release note highlights can be found here: > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > > >
[VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.99.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ The Git tag is minifi-cpp-0.99.0-RC3 The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: SHA256: c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 SHA512: d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 121 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC2)
Martin Zink pointed out that using NiFi python processors with a virtualenv crashes MiNiFi C++ on some specific Linux distributions and python versions according to our Python version compatibility checks. This seems to be a release blocking issue, described in the following Jira ticket: https://issues.apache.org/jira/browse/MINIFICPP-2360 I'm canceling RC2 due to this and will create a new RC once the issue is resolved. BR, Gabor On Sat, 4 May 2024 at 02:06, Marton Szasz wrote: > +1 (binding) > > Tried in an ubuntu:24.04 docker container, and updated the release > helper guide on Confluence with my findings. > It worked as expected. > > Tried compiling and running on a fresh Arch Linux VM, with the new > Python bootstrap: > > https://github.com/apache/nifi-minifi-cpp?tab=readme-ov-file#python-based-bootstrapping-recommended > I had to install these packages for it to work: > - general: git wget > - bootstrap: python sudo > - needed for build, but not installed by the bootstrap: autoconf > automake libtool > After installing these, I could build and run it. I tested collecting > the systemd-journald logs, and forwarding them in compressed batches > through HTTP. (ConsumeJournald -> MergeContent -> CompressContent -> > InvokeHTTP) > It worked as expected. > > Tried compiling and running on Windows 10, with the new Python > bootstrap. This was not a fresh install, so I don't have a list of > possibly missing dependencies here. > The test flow was collecting Windows Security Audit Event Logs, and > forwarding them similarly to the journald linux test, but this time it > went to the NiFi release candidate, since I was testing that, too. > The compilation was one with a fairly large set of extensions. SFTP > didn't compile, but I think that's not a dealbreaker on Windows. > Both the convenience binaries and my build worked as expected. > > Thanks for RMing! > > Marton > > On 5/2/24 6:04 PM, Gábor Gyimesi wrote: > > Minor correction for the last 2 links: > > > > 118 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.0 > > > > BR, > > Gabor > > > > On Thu, 2 May 2024 at 17:51, Gábor Gyimesi wrote: > > > >> Hello, > >> > >> I am pleased to be calling this vote for the source release of Apache > NiFi > >> MiNiFi C++ 0.99.0. > >> > >> The source tarball, some binary builds, plus signatures and digests can > be > >> found at: > >> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > >> > >> The Git tag is minifi-cpp-0.99.0-RC2 > >> The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 > >> > >> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 > >> > >> Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > >> SHA256: acbf1c05f808c6bb6852c7885212c503b79d0118d5c493921560e14d53d86270 > >> SHA512: > >> > d354469b7ce36df4203aa274856ff91b2944c4eca6f13ff83d1f7049ee208dc52809145fa7a19fc1a8c6fbb8747f2b4eac9056d13c9de2b095bf82f5669d30a8 > >> > >> Release artifacts are signed with the following key: > >> https://people.apache.org/keys/committer/lordgamez.asc > >> > >> A helpful reminder on how the release candidate verification process > works: > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > >> > >> KEYS file available here: > >> https://dist.apache.org/repos/dist/release/nifi/KEYS > >> > >> 8 issues were closed/resolved for this release: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12351771 > >> > >> Release note highlights can be found here: > >> > >> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.99.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-minifi-cpp-0.99.0 > >> [ ] +0 no opinion > >> [ ] -1 Do not release this package because... > >> >
Re: [VOTE] Release Apache NiFi 1.26.0 (RC1)
+1 (non-binding) - Verified hashes and signatures - Successfully built NiFi 1.26.0 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-26-generic - openjdk 11.0.22 2024-01-16 OpenJDK Runtime Environment (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1) OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1, mixed mode, sharing) - Apache Maven 3.6.3 - Designed and ran a simple flow - Built a docker image and tested S2S communication and HTTP data forwarding from MiNiFi C++ - Tested minifi-c2 server heartbeat and flow update with MiNiFi C++ Thank you Pierre for RMing! Regards, Gabor On Mon, 6 May 2024 at 06:33, Marton Szasz wrote: > +1 (binding) > > - Went through the helper guide, built on Ubuntu 24.04 LTS, and tested > on Ubuntu with Java 8 and Arch Linux with Java 22. > - Tested forwarding compressed logs from the MiNiFi C++ RC through HTTP, > and decompressing them on NiFi. > - Tested sending a flow definition from the MiNiFi C2 service to MiNiFi > C++. > > Thanks for the release, Pierre! > > Marton > > > On 5/6/24 5:39 AM, Mark Bean wrote: > > +1 (non-binding) > > > > Verified keys and hashes > > Performed a clean build > > Java 1.8.0_402 > > Maven 3.9.3 > > Ubuntu 22.04.4 > > > > Performed upgrade from NiFi 1.25.0 > > Started correctly. Interacted with NiFi Registry 1.25.0 normally. > > Performed upgrade of NiFi Registry from 1.25.0 > > Again, behavior and interaction between NiFi and Registry normal. > > > > Ran simple flows in a non-cluster configuration. No issues noted. > > > > Thanks Pierre for taking on the RM duties. > > > > -Mark > > > > > > On Fri, May 3, 2024 at 10:38 PM Csaba Bejan > wrote: > > > >> +1 (binding) > >> > >> Went through the helper guide and did a clean build > >> Verified signatures and hashes > >> Built on OSX 14.2.1 > >> Java version: 11.0.20, OpenJDK 64-Bit Server VM Zulu11.66+15-CA (build > >> 11.0.20+8-LTS, mixed mode) > >> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > >> Started NiFi and created a simple flow > >> Started MiNiFi and verified integration with C2 Server. Played around > with > >> the C2 protocol (Operations - Update, Transfer, Describe...) > >> Thanks for RMing, Pierre! > >> > >> Regards, > >> > >> Csaba > >> > >> > >>> On 3 May 2024, at 08:46, Pierre Villard > >> wrote: > >>> Team, > >>> > >>> I am pleased to be calling this vote for the source release of Apache > >> NiFi > >>> 1.26.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-1.26.0 > >>> > >>> The build artifacts are available on the Apache Nexus Repository: > >>> > >>> https://repository.apache.org/content/repositories/orgapachenifi-1265 > >>> > >>> Git Tag: nifi-1.26.0-RC1 > >>> Git Commit ID: 338083f6850b61cd2651e41bbd73b3cb5330d98c > >>> GitHub Commit Link: > >>> > >> > https://github.com/apache/nifi/commit/338083f6850b61cd2651e41bbd73b3cb5330d98c > >>> Checksums of nifi-1.26.0-source-release.zip > >>> > >>> SHA256: > 75ea201c12bb99672b1f075c9520b5f7df8b24e033ec47121848b351a0d47790 > >>> SHA512: > >>> > >> > 5b754d899ce8cff900d5871d44c2fda9224e69fe8a0fe9a7121f3359ed8881300e4d4d0b2fe5befea276e0495c7ebbed04cc307c18527aa7a1cea25a923a > >>> Release artifacts are signed with the following key: > >>> > >>> https://people.apache.org/keys/committer/pvillard.asc > >>> > >>> KEYS file is available on the Apache Distribution Repository: > >>> > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS > >>> > >>> Issues resolved for this version: 128 > >>> > >>> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354185 > >>> Release note highlights can be found on the project wiki: > >>> > >>> > >> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.26.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-1.26.0 > >>> [] +0 no opinion > >>> [] -1 Do not release this package because... > >> >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC1)
Canceling RC1 due to some additional temporary files made it to the source tar gz. On Thu, 2 May 2024 at 17:13, Gábor Gyimesi wrote: > Canceling RC1 due to some additional temporary files made it to the source > tar gz. > > On Thu, 2 May 2024 at 16:21, Gábor Gyimesi wrote: > >> Hello, >> >> I am pleased to be calling this vote for the source release of Apache >> NiFi MiNiFi C++ 0.99.0. >> >> The source tarball, some binary builds, plus signatures and digests can >> be found at: >> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ >> >> The Git tag is minifi-cpp-0.99.0-RC1 >> The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 >> >> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 >> >> Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: >> SHA256: 0e144c6c07008759a0eb70bd453d689ba922176cac83f30f92da5c649217781d >> SHA512: >> ee667708ee55493ab1847bd4e2cfc28c4c9940af3ceb49fc674b624ff74f090413dd649c66c5b2941fd67a76f8793d79114011f87e741b650ee5ce49926ffc21 >> >> Release artifacts are signed with the following key: >> https://people.apache.org/keys/committer/lordgamez.asc >> >> A helpful reminder on how the release candidate verification process >> works: >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 >> >> KEYS file available here: >> https://dist.apache.org/repos/dist/release/nifi/KEYS >> >> 118 issues were closed/resolved for this release: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 >> >> Release note highlights can be found here: >> >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because... >> >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC2)
Minor correction for the last 2 links: 118 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.0 BR, Gabor On Thu, 2 May 2024 at 17:51, Gábor Gyimesi wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > MiNiFi C++ 0.99.0. > > The source tarball, some binary builds, plus signatures and digests can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > The Git tag is minifi-cpp-0.99.0-RC2 > The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > SHA256: acbf1c05f808c6bb6852c7885212c503b79d0118d5c493921560e14d53d86270 > SHA512: > d354469b7ce36df4203aa274856ff91b2944c4eca6f13ff83d1f7049ee208dc52809145fa7a19fc1a8c6fbb8747f2b4eac9056d13c9de2b095bf82f5669d30a8 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/lordgamez.asc > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 8 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12351771 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.99.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-minifi-cpp-0.99.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Apache NiFi MiNiFi C++ 0.99.0 RC2 Release Helper Guide
Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/release/nifi/KEYS # Import keys file: gpg --import KEYS # Pull down nifi-minifi-cpp-0.99.0 source release artifacts for review: wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.asc wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha256 wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha512 # Verify the signature gpg --verify nifi-minifi-cpp-0.99.0-source.tar.gz.asc # Verify the hashes (sha256, sha512) match the source and what was provided in the vote email thread sha256sum nifi-minifi-cpp-0.99.0-source.tar.gz sha512sum nifi-minifi-cpp-0.99.0-source.tar.gz # Extract nifi-minifi-cpp-0.99.0-source.tar.gz tar xvzf nifi-minifi-cpp-0.99.0-source.tar.gz # Verify the build works including tests and linter checks cd nifi-minifi-cpp-0.99.0-source mkdir build && cd build && cmake .. && make package && make test && make linter # or: # ./bootstrap.sh && cd build && make package && make test && make linter # On Windows: # Install dependencies as documented: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139627733 # cd nifi-minifi-cpp-0.99.0-source # win_build_vs.bat build /P # Verify the contents contain a good README, NOTICE, and LICENSE. # Verify the git commit ID is correct # Verify the RC was branched off the correct git commit ID # Look at the resulting convenience binary as found in build/nifi-minifi-cpp-0.99.0-bin.tar.gz # Make sure the README, NOTICE, and LICENSE are present and correct # Run the resulting convenience binary and make sure it works as expected # Send a response to the vote thread indicating a +1, 0, -1 based on your findings. Thank you for your time and effort to validate the release!
[VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC2)
Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.99.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ The Git tag is minifi-cpp-0.99.0-RC2 The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: SHA256: acbf1c05f808c6bb6852c7885212c503b79d0118d5c493921560e14d53d86270 SHA512: d354469b7ce36df4203aa274856ff91b2944c4eca6f13ff83d1f7049ee208dc52809145fa7a19fc1a8c6fbb8747f2b4eac9056d13c9de2b095bf82f5669d30a8 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 8 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12351771 Release note highlights can be found here: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.99.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-minifi-cpp-0.99.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC1)
Canceling RC1 due to some additional temporary files made it to the source tar gz. On Thu, 2 May 2024 at 16:21, Gábor Gyimesi wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > MiNiFi C++ 0.99.0. > > The source tarball, some binary builds, plus signatures and digests can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > The Git tag is minifi-cpp-0.99.0-RC1 > The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > SHA256: 0e144c6c07008759a0eb70bd453d689ba922176cac83f30f92da5c649217781d > SHA512: > ee667708ee55493ab1847bd4e2cfc28c4c9940af3ceb49fc674b624ff74f090413dd649c66c5b2941fd67a76f8793d79114011f87e741b650ee5ce49926ffc21 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/lordgamez.asc > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 118 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Re: Apache NiFi MiNiFi C++ 0.99.0 RC1 Release Helper Guide
Canceling RC1 due to some additional temporary files made it to the source tar gz. On Thu, 2 May 2024 at 16:23, Gábor Gyimesi wrote: > Hello Apache NiFi community, > > Please find the associated guidance to help those interested in > validating/verifying the release so they can vote. > > # Download latest KEYS file: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > # Import keys file: > gpg --import KEYS > > # Pull down nifi-minifi-cpp-0.99.0 source release artifacts for review: > > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.asc > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha256 > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha512 > > # Verify the signature > gpg --verify nifi-minifi-cpp-0.99.0-source.tar.gz.asc > > # Verify the hashes (sha256, sha512) match the source and what was > provided in the vote email thread > sha256sum nifi-minifi-cpp-0.99.0-source.tar.gz sha512sum > nifi-minifi-cpp-0.99.0-source.tar.gz > > # Extract nifi-minifi-cpp-0.99.0-source.tar.gz > tar xvzf nifi-minifi-cpp-0.99.0-source.tar.gz > > # Verify the build works including tests and linter checks > cd nifi-minifi-cpp-0.99.0-source > mkdir build && cd build && cmake .. && make package && make test && make > linter > # or: > # ./bootstrap.sh && cd build && make package && make test && make linter > > # On Windows: > # Install dependencies as documented: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139627733 > # cd nifi-minifi-cpp-0.99.0-source > # win_build_vs.bat build /P > > # Verify the contents contain a good README, NOTICE, and LICENSE. > > # Verify the git commit ID is correct > > # Verify the RC was branched off the correct git commit ID > > # Look at the resulting convenience binary as found in > build/nifi-minifi-cpp-0.99.0-bin.tar.gz > > # Make sure the README, NOTICE, and LICENSE are present and correct > > # Run the resulting convenience binary and make sure it works as expected > > # Send a response to the vote thread indicating a +1, 0, -1 based on your > findings. > > Thank you for your time and effort to validate the release! >
Apache NiFi MiNiFi C++ 0.99.0 RC1 Release Helper Guide
Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/release/nifi/KEYS # Import keys file: gpg --import KEYS # Pull down nifi-minifi-cpp-0.99.0 source release artifacts for review: wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.asc wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha256 wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/nifi-minifi-cpp-0.99.0-source.tar.gz.sha512 # Verify the signature gpg --verify nifi-minifi-cpp-0.99.0-source.tar.gz.asc # Verify the hashes (sha256, sha512) match the source and what was provided in the vote email thread sha256sum nifi-minifi-cpp-0.99.0-source.tar.gz sha512sum nifi-minifi-cpp-0.99.0-source.tar.gz # Extract nifi-minifi-cpp-0.99.0-source.tar.gz tar xvzf nifi-minifi-cpp-0.99.0-source.tar.gz # Verify the build works including tests and linter checks cd nifi-minifi-cpp-0.99.0-source mkdir build && cd build && cmake .. && make package && make test && make linter # or: # ./bootstrap.sh && cd build && make package && make test && make linter # On Windows: # Install dependencies as documented: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139627733 # cd nifi-minifi-cpp-0.99.0-source # win_build_vs.bat build /P # Verify the contents contain a good README, NOTICE, and LICENSE. # Verify the git commit ID is correct # Verify the RC was branched off the correct git commit ID # Look at the resulting convenience binary as found in build/nifi-minifi-cpp-0.99.0-bin.tar.gz # Make sure the README, NOTICE, and LICENSE are present and correct # Run the resulting convenience binary and make sure it works as expected # Send a response to the vote thread indicating a +1, 0, -1 based on your findings. Thank you for your time and effort to validate the release!
[VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC1)
Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.99.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ The Git tag is minifi-cpp-0.99.0-RC1 The Git commit ID is 63e213efeefae112e8094e2db7292bdb03fb6ce3 https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=63e213efeefae112e8094e2db7292bdb03fb6ce3 Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: SHA256: 0e144c6c07008759a0eb70bd453d689ba922176cac83f30f92da5c649217781d SHA512: ee667708ee55493ab1847bd4e2cfc28c4c9940af3ceb49fc674b624ff74f090413dd649c66c5b2941fd67a76f8793d79114011f87e741b650ee5ce49926ffc21 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 118 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [DISCUSS] MiNiFi C++ 1.0.0-M1 release
As there seems to be no objections, I will move forward with the release with the new 0.99.0 version proposal. BR, Gabor On Thu, 25 Apr 2024 at 15:41, Marton Szasz wrote: > There is a limitation of CMake that it doesn't allow anything other than > numbers in the version. MiNiFi C++ uses CMake as its build system > generator, so this affects us. The initial idea was to go with 1.0.0 > internally, and only specify the -M1 suffix in the package name, git > tag, etc. > > We had a conversation with the c++ agent contributors, where I proposed > to go with 0.99.0 instead, which still signifies that this is "close to > 1.0", but it may avoid confusion when someone looks at the internal > version metadata. Not sure if it shows up anywhere on Linux, but on > Windows, this version is visible in 'Programs and Features', and in the > PE metadata of our binaries (minifi.exe, extension DLLs), where users > would only see 1.0.0, even for the milestone releases, if we stayed with > 1.0.0 as the CMake-internal version. > > I want to propose to the wider community as well to go with 0.99.0 as > the first MiNiFi C++ milestone release version for 1.0, both internally > in CMake and externally in the package name, git tag, and anywhere else > where we show version. We can continue with 0.99.1 and so on for future > pre-1.0 milestone releases. We already agreed to this change in a > private conversation with the MiNiFi C++ core contributors, so I'll go > ahead and change the version in Jira, etc, unless anyone objects. > > Thanks, > Marton > > On 4/18/24 1:14 PM, Arpad Boda wrote: > > +1 and thanks for RMing! > > > > The python support in this new AI era is great! > > > > On Thu, Apr 18, 2024 at 1:01 PM Marton Szasz wrote: > > > >> +1, thanks for RMing. > >> > >> I think we should follow the progression of the new NiFi Python API with > >> the MiNiFi C++ 1.0 milestone releases, and when NiFi 2.0 is out, we > >> could release MiNiFi C++ 1.0, and commit to backwards-compatibility to > >> this API. > >> > >> I'd exclude the C++ API, and the old MiNiFi C++-style Python and Lua > >> scripting APIs out of the backwards compatibility commitment. > >> > >> Thanks, > >> Marton > >> > >> On 4/16/24 6:41 PM, Pierre Villard wrote: > >>> I'm a +1 with this approach. Being able to use the Python extensions in > >>> MiNiFi cpp is great! > >>> > >>> Thanks, > >>> Pierre > >>> > >>> Le mar. 16 avr. 2024 à 18:39, Gábor Gyimesi a > >> écrit : > >>>> Hi community, > >>>> > >>>> I'd like to initiate a discussion about the next release of MiNiFi > C++. > >> The > >>>> last release was more than seven months ago, and there have been many > >> new > >>>> features, bug fixes and stability improvements committed to the > >> development > >>>> branch since then: 107 tickets closed, over 122 commits as of today. > >>>> > >>>> I would be happy to take on RM duties for this release. > >>>> > >>>> Notable features and improvements since the 0.15.0 release: > >>>> > >>>> New notable features: > >>>> - Added support for using NiFi 2.0 Python processors in MiNiFi C++ > >>>> - This also includes several improvements to the previous MiNiFi > >> style > >>>> python processors, like additional property options, custom > >> relationships > >>>> and virtualenv support > >>>> - Added new python based multiplatform bootstrap script > >>>> - Added encryption support for sensitive properties in flow > >> configuration > >>>> - Releasing Windows installer now can be done (and will be done) under > >> the > >>>> Apache license > >>>> - Added support for service installation on MacOS > >>>> - Added C2 debug command to MiNiFi Controller > >>>> - Added support for setting MiNiFi properties from command line > >>>> - Added system load average field to C2 and Prometheus metrics > >>>> - Added support for manually configuring RocksDB options > >>>> - Added custom delimiter property for ListenTCP processor > >>>> - Added bandwidth limit properties to InvokeHTTP processor > >>>> - Added JSON flow configuration examples > >>>> > >>>> New processors: > >>>> - Added PutSmb, FetchSmb and ListSmb pr
[DISCUSS] MiNiFi C++ 1.0.0-M1 release
Hi community, I'd like to initiate a discussion about the next release of MiNiFi C++. The last release was more than seven months ago, and there have been many new features, bug fixes and stability improvements committed to the development branch since then: 107 tickets closed, over 122 commits as of today. I would be happy to take on RM duties for this release. Notable features and improvements since the 0.15.0 release: New notable features: - Added support for using NiFi 2.0 Python processors in MiNiFi C++ - This also includes several improvements to the previous MiNiFi style python processors, like additional property options, custom relationships and virtualenv support - Added new python based multiplatform bootstrap script - Added encryption support for sensitive properties in flow configuration - Releasing Windows installer now can be done (and will be done) under the Apache license - Added support for service installation on MacOS - Added C2 debug command to MiNiFi Controller - Added support for setting MiNiFi properties from command line - Added system load average field to C2 and Prometheus metrics - Added support for manually configuring RocksDB options - Added custom delimiter property for ListenTCP processor - Added bandwidth limit properties to InvokeHTTP processor - Added JSON flow configuration examples New processors: - Added PutSmb, FetchSmb and ListSmb processor for SMB networking protocol support - Added PushGrafanaLokiGrpc and PushGrafanaLokiREST processors for pushing logs to Grafana Loki - Added JoltTransform to use Jolt JSON transformations - Added SplitText processor - Added AttributeRollingWindow processor Changes and improvements: - Dropped support for disabling peer verification in InvokeHTTP - Corrupt flow files are now filtered to avoid errors in the flow - Using administrative yield duration instead of onschedule retry interval in scheduling adjusting to NiFi's functionality - Fixed high disk IO usage issue with MergeContent - Fixed the site-to-site transfer or large files - Fixed memory leak caused by unused loggers - Fixed yielding processors to still respect scheduling period Upgraded dependencies: - Upgraded OpenSSL to version 3.3.0 - Upgraded AWS SDK to version 1.11.219 with support for new AWS regions - Upgraded libuvc to version 0.0.7 - Upgraded docker base image to alpine:3.18 - Upgraded Sol2 to version 3.3.0 With the current maturity level of the project and with the support for NiFi 2.0 style python processors and json flow configuration, I suggest releasing it as version 1.0.0-M1 milestone release. Do you agree it is time for a new release? Do you agree with the suggested version? Are there any blockers that we should definitely include in this release? Thanks, Gabor
Re: [DISCUSS] New Project Repository for Python Extensions?
Hi David, MiNiFi C++ had had a Python API before, using Python's stable C API, but the processors had a different, simpler format like this following example: https://github.com/apache/nifi-minifi-cpp/blob/main/extensions/python/pythonprocessors/examples/GaussianDistributionWithNumpy.py Our goal was to be able to support NiFi's Python API, with the ease of only copying the Python processor file to MiNiFi C++'s configured python processor path, and use them in the flow config the same way as the original MiNiFi C++ style python processors. There is already an open PR for supporting this for NiFi's FlowFileTransform processor types (as of now MiNiFi C++ does not support record based flow file processing): https://github.com/apache/nifi-minifi-cpp/pull/1712 and also an open PR for supporting virtual environments: https://github.com/apache/nifi-minifi-cpp/pull/1721 as previously MiNiFi C++ only supported system installed Python packages. The implementation uses the same C API bindings as before, importing NiFi's nifiapi adapted to MiNiFi C++'s python API to be able to use NiFi's Python processors. There are still a few limitations due to the differences between NiFi and MiNiFi C++ implementations which are listed here: https://github.com/apache/nifi-minifi-cpp/blob/d27430260c8c35dac52011bdb31b22b36e10539d/extensions/python/PYTHON.md Some of these limitations are being addressed by these jira tickets in this epic: https://issues.apache.org/jira/browse/MINIFICPP-2272 I tested all the available Python processors (aside from RecordTransform processors) of NiFi 2.0.0-M2 and they seem to be working with MiNiFi C++ with these PRs, so it looks promising. Regards, Gabor Gyimesi On Thu, 1 Feb 2024 at 19:03, David Handermann wrote: > Hi Gabor, > > Thanks for the reply. > > It is helpful to know about the progress of Python Processor support > in MiNiFi C++. Is the goal to support the same NiFi Python API as > implemented for NiFi itself? > > The goal of a separate repository for Python extensions would be to > keep it self-contained for testing and releasing. From that > perspective, it would have a dependency on a declared version of the > NiFi Python API, and would include automated build workflows for > testing. > > For the NiFi framework components, there would still need to be > internal components that support testing implementations of Python > APIs, but the Python Extensions repository would have its own > decoupled set of tests. > > Regards, > David Handermann > > On Thu, Feb 1, 2024 at 11:05 AM Gábor Gyimesi wrote: > > > > Hi David, > > > > Currently we are in the process of implementing support for the NiFi > python > > processors in MiNiFi C++. Probably in the next open source release this > > feature will be available, so the available NiFi Python processors will > be > > usable in MiNiFi C++ as well. I think this idea would help with the > > collaboration of supporting these processors in both Java and C++ > projects. > > It would certainly make release verification easier to be able to > > concentrate only on the Python processors if they are released > separately. > > > > My concern is how would the automatic testing and verification would work > > in this scenario? Would all the testing of the Python processors be moved > > to the new repository and would be tested there separately, with both > NiFi > > and MiNiFi C++, or only with NiFi, or all of the testing would remain in > > the respective client repositories? > > > > Regards, > > Gabor Gyimesi > > > > On Fri, 26 Jan 2024 at 14:11, David Handermann < > exceptionfact...@apache.org> > > wrote: > > > > > Pierre, > > > > > > Thanks for the reply, and noting the potential concern with the > > > ability to find these components. > > > > > > I think there are several ways we can address this concern, both for > > > optional Java components, and for Python components in a separate > > > repository. > > > > > > For Python components in particular, we could add direct links to > > > published versions on the main download page, calling out their > > > availability in the official PyPI repository. Although this would need > > > to be denoted as a non-official release channel for Apache purposes, > > > this is common practice in other projects, and follows the approach we > > > already have for container images on Docker Hub. > > > > > > In addition to linking from the download page, we could publish the > > > generated documentation for these components. The current process for > > > publishing generated documentation is based on the convenience b
Re: [DISCUSS] New Project Repository for Python Extensions?
Hi David, Currently we are in the process of implementing support for the NiFi python processors in MiNiFi C++. Probably in the next open source release this feature will be available, so the available NiFi Python processors will be usable in MiNiFi C++ as well. I think this idea would help with the collaboration of supporting these processors in both Java and C++ projects. It would certainly make release verification easier to be able to concentrate only on the Python processors if they are released separately. My concern is how would the automatic testing and verification would work in this scenario? Would all the testing of the Python processors be moved to the new repository and would be tested there separately, with both NiFi and MiNiFi C++, or only with NiFi, or all of the testing would remain in the respective client repositories? Regards, Gabor Gyimesi On Fri, 26 Jan 2024 at 14:11, David Handermann wrote: > Pierre, > > Thanks for the reply, and noting the potential concern with the > ability to find these components. > > I think there are several ways we can address this concern, both for > optional Java components, and for Python components in a separate > repository. > > For Python components in particular, we could add direct links to > published versions on the main download page, calling out their > availability in the official PyPI repository. Although this would need > to be denoted as a non-official release channel for Apache purposes, > this is common practice in other projects, and follows the approach we > already have for container images on Docker Hub. > > In addition to linking from the download page, we could publish the > generated documentation for these components. The current process for > publishing generated documentation is based on the convenience binary, > but with some adjustments, we could publish the documentation for the > Python components as well. This is a good prompt to start doing this > for the optional Java components, and I plan to look at doing this for > the next release with optional Java components. > > To your last question, it is worth noting that any binary releases > would fall into the category of convenience builds. Initially, I think > the NiFi framework release would not include the Python extension > components. However, having a few short steps on installation, linked > from the download page, seems like it would provide a way forward. > > Regards, > David Handermann > > On Fri, Jan 26, 2024 at 1:22 AM Pierre Villard > wrote: > > > > Hi David, > > > > While I agree with your summary, I have a concern here which is about > user > > awareness of this feature. We've seen in the past: as soon as we don't > > include NARs in the convenience binary, we see that users have no clue > > about those NARs (and some are super powerful/useful). I agree that > python > > is a bit different because it requires a user action to enable it in the > > first place but I still think that including the components in the > > convenience binary of Apache NiFi would drive user awareness, adoption, > etc. > > > > If we have a separated repo with its own release cycle can we imagine a > > process where, when releasing Apache NiFi, it'd include whatever is the > > latest version of the Python repo? Or something along those lines? > > > > Pierre > > > > Le ven. 26 janv. 2024 à 08:01, David Handermann < > exceptionfact...@apache.org> > > a écrit : > > > > > Team, > > > > > > As we get closer to a full release of Apache NiFi 2.0.0, we have an > > > important opportunity to set the direction for future development of > > > Python-based Processors. > > > > > > The introduction of native Python support presents a number of new > > > integration opportunities, and it also raises questions about > > > maintenance and versioning. As the journey to NiFi 2.0.0 has shown, it > > > requires significant effort to coordinate maintenance and > > > modernization across hundreds of project modules. Although the > > > internal project structure has maintained helpful separation of API > > > and implementation, the current release strategy highlights the > > > challenges of verifying multiple layers of changes. Introducing a new > > > programming language provides greater possibilities, but also makes it > > > more difficult to maintain a single repository with a single > > > versioning strategy. > > > > > > I propose creating a new Git repository named nifi-python-extensions, > > > which would have its own versioning and release process. This would > > > contain the extensions now under the module of the same name in the > > > NiFi repository. Having a separate repository and release process for > > > Python-based extensions has the following advantages: > > > > > > 1. Clean separation between NiFi APIs for Python and Python-based > > > Processors > > > 2. Independent release cycles for Python-based Processors > > > 3. Focused release verification and testing on Python-based modules > >
Re: [VOTE] Release Apache NiFi 1.25.0 (RC1)
+1 non-binding - Verified hashes and signatures - Successfully built NiFi 1.25.0 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-15-generic - openjdk 11.0.21 2023-10-17 OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) - Apache Maven 3.6.3 - Designed and run a flow merging, compressing, uploading data to S3 successfully - Built a docker image and tested S2S communication and HTTP data forwarding from MiNiFi C++ Thanks for RMing Pierre! Regards, Gabor On Fri, 26 Jan 2024 at 16:08, Gábor Gyimesi wrote: > Thanks for the clarification David! > > Regards, > Gabor > > On Fri, 26 Jan 2024 at 16:01, David Handermann < > exceptionfact...@apache.org> wrote: > >> Hi Gabor, >> >> The Docker Hub release process is independent of the source release >> process, and is technically considered a convenience binary build. >> From that perspective, I don't think it is a concern for this release >> vote of 1.25.0, but worth noting. >> >> Regards, >> David Handermann >> >> On Fri, Jan 26, 2024 at 8:32 AM Gábor Gyimesi >> wrote: >> > >> > Hi Pierre, >> > >> > I had a successful clean build, but when I built a docker image the tag >> was >> > still set to 1.24.0. It seems that the docker files were not updated to >> > version 1.25.0. I'm not sure if it's a release blocking issue for the >> > distributed source, or it can be updated before updating the >> > dockerhub image? >> > >> > Regards, >> > Gabor >> > >> > On Thu, 25 Jan 2024 at 20:20, Joe Witt wrote: >> > >> > > +1 binding. >> > > >> > > Full clean build with contrib check and the usual checks works out. >> Ran >> > > simple local flow and checks out as well. Checked latest commit. >> > > >> > > Thanks Pierre! >> > > >> > > On Thu, Jan 25, 2024 at 11:53 AM Pierre Villard < >> > > pierre.villard...@gmail.com> >> > > wrote: >> > > >> > > > Team, >> > > > >> > > > I am pleased to be calling this vote for the source release of >> Apache >> > > NiFi >> > > > 1.25.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-1.25.0 >> > > > >> > > > The build artifacts are available on the Apache Nexus Repository: >> > > > >> > > > >> https://repository.apache.org/content/repositories/orgapachenifi-1263 >> > > > >> > > > Git Tag: nifi-1.25.0-RC1 >> > > > Git Commit ID: 6ecc398d3f92425447e43242af4992757e25b3c5 >> > > > GitHub Commit Link: >> > > > >> > > > >> > > >> https://github.com/apache/nifi/commit/6ecc398d3f92425447e43242af4992757e25b3c5 >> > > > >> > > > Checksums of nifi-1.25.0-source-release.zip >> > > > >> > > > SHA256: >> 6a14b35bf5beb4ae3fcf76df8d09676e61c6bc309a97dc6785eae84b7cbaef78 >> > > > SHA512: >> > > > >> > > > >> > > >> 1ffb2586ce9591ce2c5aa39fdec43a89ffd29081a31d51dc95dd953cb7f94584d0a0171bb1ba7c9495f431aec3770d324dbabb319b01bb6fdce5a0a00426fffa >> > > > >> > > > Release artifacts are signed with the following key: >> > > > >> > > > https://people.apache.org/keys/committer/pvillard.asc >> > > > >> > > > KEYS file is available on the Apache Distribution Repository: >> > > > >> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS >> > > > >> > > > Issues resolved for this version: 103 >> > > > >> > > > >> > > > >> > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353860 >> > > > >> > > > Release note highlights can be found on the project wiki: >> > > > >> > > > >> > > > >> > > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.25.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-1.25.0 >> > > > [] +0 no opinion >> > > > [] -1 Do not release this package because... >> > > > >> > > >> >
Re: [VOTE] Release Apache NiFi 1.25.0 (RC1)
Thanks for the clarification David! Regards, Gabor On Fri, 26 Jan 2024 at 16:01, David Handermann wrote: > Hi Gabor, > > The Docker Hub release process is independent of the source release > process, and is technically considered a convenience binary build. > From that perspective, I don't think it is a concern for this release > vote of 1.25.0, but worth noting. > > Regards, > David Handermann > > On Fri, Jan 26, 2024 at 8:32 AM Gábor Gyimesi wrote: > > > > Hi Pierre, > > > > I had a successful clean build, but when I built a docker image the tag > was > > still set to 1.24.0. It seems that the docker files were not updated to > > version 1.25.0. I'm not sure if it's a release blocking issue for the > > distributed source, or it can be updated before updating the > > dockerhub image? > > > > Regards, > > Gabor > > > > On Thu, 25 Jan 2024 at 20:20, Joe Witt wrote: > > > > > +1 binding. > > > > > > Full clean build with contrib check and the usual checks works out. > Ran > > > simple local flow and checks out as well. Checked latest commit. > > > > > > Thanks Pierre! > > > > > > On Thu, Jan 25, 2024 at 11:53 AM Pierre Villard < > > > pierre.villard...@gmail.com> > > > wrote: > > > > > > > Team, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi > > > > 1.25.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-1.25.0 > > > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1263 > > > > > > > > Git Tag: nifi-1.25.0-RC1 > > > > Git Commit ID: 6ecc398d3f92425447e43242af4992757e25b3c5 > > > > GitHub Commit Link: > > > > > > > > > > > > https://github.com/apache/nifi/commit/6ecc398d3f92425447e43242af4992757e25b3c5 > > > > > > > > Checksums of nifi-1.25.0-source-release.zip > > > > > > > > SHA256: > 6a14b35bf5beb4ae3fcf76df8d09676e61c6bc309a97dc6785eae84b7cbaef78 > > > > SHA512: > > > > > > > > > > > > 1ffb2586ce9591ce2c5aa39fdec43a89ffd29081a31d51dc95dd953cb7f94584d0a0171bb1ba7c9495f431aec3770d324dbabb319b01bb6fdce5a0a00426fffa > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > Issues resolved for this version: 103 > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353860 > > > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.25.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-1.25.0 > > > > [] +0 no opinion > > > > [] -1 Do not release this package because... > > > > > > > >
Re: [VOTE] Release Apache NiFi 1.25.0 (RC1)
Hi Pierre, I had a successful clean build, but when I built a docker image the tag was still set to 1.24.0. It seems that the docker files were not updated to version 1.25.0. I'm not sure if it's a release blocking issue for the distributed source, or it can be updated before updating the dockerhub image? Regards, Gabor On Thu, 25 Jan 2024 at 20:20, Joe Witt wrote: > +1 binding. > > Full clean build with contrib check and the usual checks works out. Ran > simple local flow and checks out as well. Checked latest commit. > > Thanks Pierre! > > On Thu, Jan 25, 2024 at 11:53 AM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.25.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-1.25.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1263 > > > > Git Tag: nifi-1.25.0-RC1 > > Git Commit ID: 6ecc398d3f92425447e43242af4992757e25b3c5 > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/6ecc398d3f92425447e43242af4992757e25b3c5 > > > > Checksums of nifi-1.25.0-source-release.zip > > > > SHA256: 6a14b35bf5beb4ae3fcf76df8d09676e61c6bc309a97dc6785eae84b7cbaef78 > > SHA512: > > > > > 1ffb2586ce9591ce2c5aa39fdec43a89ffd29081a31d51dc95dd953cb7f94584d0a0171bb1ba7c9495f431aec3770d324dbabb319b01bb6fdce5a0a00426fffa > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 103 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353860 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.25.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-1.25.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC4)
+1 non-binding Went through the same steps of the previous RC verification: - Verified hashes and signatures - Successfully built NiFi with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-14-generic - java 21 2023-09-19 LTS Java(TM) SE Runtime Environment (build 21+35-LTS-2513) Java HotSpot(TM) 64-Bit Server VM (build 21+35-LTS-2513, mixed mode, sharing) - Apache Maven 3.6.3 - Built a containerized version of NiFi and tested site to site use cases and http communication (using InvokeHTTP-ListenHTTP) between NiFi and MiNiFi C++ Additionally verified the fix for HandleHttpRequest processor with a simple flow, and it works as expected. Thanks David! Regards, Gabor On Fri, 26 Jan 2024 at 03:30, David Handermann wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M2. > > 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 and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1264 > > Git Tag: nifi-2.0.0-M2-RC4 > Git Commit ID: 640b7bdfbbb8842f057a9bf49dc2b9b5d092abda > GitHub Commit Link: > > https://github.com/apache/nifi/commit/640b7bdfbbb8842f057a9bf49dc2b9b5d092abda > > Checksums of nifi-2.0.0-M2-source-release.zip > > SHA256: 1946eceb3ae4f541545e93ddc6dd2cbe2a3302a6a46e6c584f3ffc1c1bd1e18b > SHA512: > e8e67e1e67359553479c0721a1c49ae6706cc6882eadf92e1f5ccc2619637ab87119a06221980d4c34d99b7b6d9a2138c77440b407074090e727b5d4447ab799 > > 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: 214 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2 > > 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-M2 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC3)
+1 non-binding - Verified hashes and signatures - Successfully built NiFi with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-14-generic - java 21 2023-09-19 LTS Java(TM) SE Runtime Environment (build 21+35-LTS-2513) Java HotSpot(TM) 64-Bit Server VM (build 21+35-LTS-2513, mixed mode, sharing) - Apache Maven 3.6.3 - Designed and ran a flow with S3 upload successfully - Built a containerized version of NiFi and tested site to site use cases and http communication between NiFi and MiNiFi C++ Thanks for RMing David! Regards, Gabor On Thu, 25 Jan 2024 at 15:46, Robert Fellows wrote: > +1 non-binding > > *verified hashes* > > *built with:* > openjdk version "21.0.1" 2023-10-17 LTS > OpenJDK Runtime Environment Zulu21.30+15-CA (build 21.0.1+12-LTS) > OpenJDK 64-Bit Server VM Zulu21.30+15-CA (build 21.0.1+12-LTS, mixed mode, > sharing) > > General usage of the application looks good. Added a couple of the new > processors and services without issue. > > > On Thu, Jan 25, 2024 at 8:11 AM 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-M2. > > > > 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 and the convenience binaries are available > > on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1262 > > > > Git Tag: nifi-2.0.0-M2-RC3 > > Git Commit ID: 439ac5f596fe90d2591376caec1499ed86abfd6b > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/439ac5f596fe90d2591376caec1499ed86abfd6b > > > > Checksums of nifi-2.0.0-M2-source-release.zip > > > > SHA256: 0637647ba7b6b8f0743cf00d95dd3e99250f2737ae9583daee511477cad22847 > > SHA512: > > > 56d6c196ec64884c56a65278f7dd32cc62f1595ff5b2ec37403dcd54b7757a9ac70aa75a50ee6f61237e37b486d32b1ebbf95a4e38a2ea5dc7f694c779d5c6c4 > > > > 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: 207 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2 > > > > 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-M2 > > [] +0 no opinion > > [] -1 Do not release this package because... > > > > > -- > --- > Rob Fellows >
Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)
Hi, I've also found an issue with RC earlier today, that the Minifi C2 server is not working anymore with Minifi C++. It seems that the Jetty server upgrade which was part of NIFI-11703 ( https://github.com/apache/nifi/pull/8197) broke the compatibility and now we are getting 403 Forbidden response in the heartbeats: 2024-01-22 15:54:47,262 DEBUG [qtp443721024-38] o.s.security.web.csrf.CsrfFilter Invalid CSRF token found for http://localhost:10090/c2/config/heartbeat 2024-01-22 15:54:47,263 DEBUG [qtp443721024-38] o.s.s.web.access.AccessDeniedHandlerImpl Responding with 403 status code Kalman Jantner is working on the issue, maybe this fix should also be included in the next RC. BR, Gabor On Mon, 22 Jan 2024 at 17:08, Dan S wrote: > Joe, > I do not have any specific settings.xml. > > Chris, > Before building I had wiped away my local Maven repo per the optional step > in Release Candidate Verification > < > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > On Mon, Jan 22, 2024 at 11:05 AM Chris Sampson > wrote: > > > Maven might have got itself confused. Could you try clearing out your > > .m2/repository (at least if anything in the org/apache/nifi directories)? > > > > Note that if you delete the whole local repo, then the build will need to > > re-download all 3rd party libraries too, so things will take longer. > > > > On the new UI front, should it be covered by the include-all profile in > the > > nifi-assembly (I don't think it is currently, but that's maybe > intentional > > and in the cards to change later one it's more stable)? > > > > On Mon, 22 Jan 2024, 15:58 Dan S, wrote: > > > > > ./mvnw -T 1C clean install -Pcontrib-check > > > > > > On Mon, Jan 22, 2024 at 10:55 AM David Handermann < > > > exceptionfact...@apache.org> wrote: > > > > > > > Dan, > > > > > > > > Thanks for noting this build behavior. > > > > > > > > The release candidate process does not publish artifacts to the Maven > > > > Central repository. The RC build only publishes artifacts to the > > > > Apache Nexus staging repository. When running the standard full > > > > rebuild as described in the release verification steps, it should not > > > > try to retrieve release versions at all. Can you provide the command > > > > you used for the initial build? > > > > > > > > Regards, > > > > David Handermann > > > > > > > > On Mon, Jan 22, 2024 at 9:52 AM Dan S wrote: > > > > > > > > > > Sorry typo in my previous email > > > > > would like to bring to your attention that I had a problem > building > > as > > > > > certain dependencies did seem to be present in Maven repos. > > > > > would like to bring to your attention that I had a problem > building > > as > > > > > certain dependencies did not seem to be present in Maven repos. > > > > > > > > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S wrote: > > > > > > > > > > > David, > > > > > > Despite cancelling RC1 I would like to bring to your attention > > that > > > I > > > > had > > > > > > a problem building as certain dependencies did seem to be present > > in > > > > Maven > > > > > > repos. > > > > > > I initially got > > > > > > > > > > > >> Could not resolve dependencies for project > > > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following > > > > artifacts > > > > > >> could not be resolved: > > > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 > > > > > >> (absent): Could not find artifact > > > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central ( > > > > > >> https://repo.maven.apache.org/maven2) > > > > > > > > > > > > > > > > > > I tried resuming and I had to manually resume with the following > as > > > it > > > > > > errored each time. > > > > > > > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf > :nifi-stateless-nar > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf > > :nifi-salesforce-nar > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf > :nifi-airtable-nar > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf > > > > :nifi-box-services-api-nar > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar > > > > > > > > > > > > > > > > > > At the last command I got an error with > > > > > > > > > > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could > > not > > > > > >> resolve dependencies for project > > > > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following > > > artifacts > > > > could > > > > > >> not be resolved: > > org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 > > > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 > > > > (absent): > > > > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not > found > > in > > > > > >> https://repo.maven.apache.org/maven2 during a previous attempt. > > > This > > > > > >> failure was cached in the local repository and resolution is not
Re: [VOTE] Release Apache NiFi 1.24.0 (RC5)
+1 (non-binding) Went through the same verification steps as per the previous RC, and LGTM: - Verified binary hashes and signatures - Successfully built NiFi with contrib-check using: - Apache Maven 3.6.3 - openjdk version "11.0.20.1" 2023-08-24 - Ubuntu 22.04 6.2.0-36-generic - Designed and ran some simple flows successfully - Tested minifi-c2 server heartbeats and flow update successfully with MiNiFi C++ - Tested communication between MiNiFi C++ and NiFi using InvokeHTTP - ListenHTTP processors and using Site 2 Site functionality with RemoteProcessGroup Thanks Pierre! BR, Gabor On Thu, 23 Nov 2023 at 16:14, Pierre Villard wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.24.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-1.24.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1251 > > Git Tag: nifi-1.24.0-RC5 > Git Commit ID: 5241f434829ca46a26a475600ef7c00e1e271e37 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/5241f434829ca46a26a475600ef7c00e1e271e37 > > Checksums of nifi-1.24.0-source-release.zip > > SHA256: 715eb61cdc017a5f7ba4d845ae962fdf83d389829db2a8948be14f99f2cc8272 > SHA512: > > 574147002b905ef64447edec0c7308f4fc3a97b3c7f01edca05464b2b418bcd3922f956d093736014443eec88ceba36af81df37398c5fe23a1288235b79d7306 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 285 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353443 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.24.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-1.24.0 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC6)
+1 (non-binding) Went through the same verification process as per the previous RC, LGTM: - Verified binary hashes and signatures - Successfully built NiFi with contrib-check using: - Apache Maven 3.6.3 - Java 21 2023-09-19 LTS - Ubuntu 22.04 6.2.0-36-generic - Designed and ran some simple flows successfully - Tested minifi-c2 server successfully with MiNiFi C++ (using a draft of the change conforming the new header requirements https://issues.apache.org/jira/browse/MINIFICPP-2244) - Built and started docker container successfully from nifi-docker/dockerhub/Dockerfile Thanks David! Best Regards, Gabor On Thu, 23 Nov 2023 at 03:49, David Handermann wrote: > Team, > > Thank you for your patience and continued support in reviewing these > release candidates. > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M1. > > 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-M1 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1250 > > Git Tag: nifi-2.0.0-M1-RC6 > Git Commit ID: 49fa0d86746f544e294b4ba04b2795d426ba0271 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/49fa0d86746f544e294b4ba04b2795d426ba0271 > > Checksums of nifi-2.0.0-M1-source-release.zip > > SHA256: 1a0271c35f585a8e49c5e578422a8e3910fbfc50069a7c875bc6cec5a056eb91 > SHA512: > 99e824a0bce109bde84218b914487fd44ba344d5ae9d8fbed9982b41dc2ee7e57b6dd30550c17a4868d43afd900705c48ec48d5e9e63a1b4130c79858f64963c > > 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: 959 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1 > > 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-M1 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC5)
+1 (non-binding) - Verified binary hashes and signatures - Successfully built NiFi with contrib-check using: - Apache Maven 3.6.3 - Java 21 2023-09-19 LTS - Ubuntu 22.04 6.2.0-36-generic - Designed and ran some simple flows successfully - Tested minifi-c2 server successfully with MiNiFi C++ (using a draft of the change conforming the new header requirements https://issues.apache.org/jira/browse/MINIFICPP-2244) - Built and started docker container successfully from nifi-docker/dockerhub/Dockerfile verifying NIFI-12396 Thanks David for RMing! Best Regards, Gabor On Tue, 21 Nov 2023 at 23:40, David Handermann wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M1. > > 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-M1 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1248 > > Git Tag: nifi-2.0.0-M1-RC5 > Git Commit ID: f81a3597d40f3fe6df93d55347a11474ee6af2c8 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/f81a3597d40f3fe6df93d55347a11474ee6af2c8 > > Checksums of nifi-2.0.0-M1-source-release.zip > > SHA256: 217096b30c211b8fb6bd069832416b507b258f335d7301772a8c047f470a4b30 > SHA512: > 949849c59d2d8a2d0a441fd14c718f97cfb86c72fdd2de9a954a5829eebad6f9ad60622ecc6db200e246f77f771530be20f47793b3a8a18d2ceed252223139ee > > 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: 958 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1 > > 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-M1 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.24.0 (RC4)
+1 (non-binding) - Verified binary hashes and signatures - Successfully built NiFi with contrib-check using: - Apache Maven 3.6.3 - openjdk version "11.0.20.1" 2023-08-24 - Ubuntu 22.04 6.2.0-36-generic - Designed and ran some simple flows successfully - Tested minifi-c2 server heartbeats and flow update successfully with MiNiFi C++ - Tested communication between MiNiFi C++ and NiFi using InvokeHTTP - ListenHTTP processors and using Site 2 Site functionality with RemoteProcessGroup Thanks Pierre! BR, Gabor On Mon, 20 Nov 2023 at 20:13, Pierre Villard wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.24.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-1.24.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1247 > > Git Tag: nifi-1.24.0-RC4 > Git Commit ID: 6029cd00c032c0596f0d4211c206762895de120b > GitHub Commit Link: > > https://github.com/apache/nifi/commit/6029cd00c032c0596f0d4211c206762895de120b > > Checksums of nifi-1.24.0-source-release.zip > > SHA256: 1c2d7d94abf7586cc014cea041852796882bd41ced449e950481a0033e8e3abc > SHA512: > > 121cd42b61100e170cd2f3716077aaf099d1e2759355432d949239e6ccd1ee25aa6b06d306a4bc1318f9717b838687127594d223b448cae994680a23d2a2f04c > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 283 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353443 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.24.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-1.24.0 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC4)
It seems the missing dependency is the "python3-venv" package from the nifi-docker/dockerhub/Dockerfile, adding the package solves the problem and NiFi starts without a problem inside the container. BR, Gabor On Tue, 21 Nov 2023 at 13:44, Gábor Gyimesi wrote: > -1 (non-binding) > > Thank you David for handling the release! > > - Verified binary hashes and signatures > - Successfully built NiFi with contrib-check using: > - Apache Maven 3.6.3 > - Java 21 2023-09-19 LTS > - Ubuntu 22.04 6.2.0-36-generic > - Ran some simple flows successfully > - Tested minifi-c2 server successfully with MiNiFi C++ (using a draft of > the change conforming the new header requirements > https://issues.apache.org/jira/browse/MINIFICPP-2244) > > One issue I encountered: > Built a docker image using the nifi-docker/dockerhub/Dockerfile dockerfile > and the binaries provided at > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M1/ but the NiFi > startup failed with the following error: "Failed to communicate with Python > Controller". > The PythonBridge class may have some dependency that is missing from the > docker image for handling the python processors. As this issue may block > the release of the new docker image on Docker Hub it may be worth > investigating before releasing this version. > > Best Regards, > Gabor > > > > On Mon, 20 Nov 2023 at 18:01, 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-M1. >> >> 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-M1 >> >> The build artifacts are available on the Apache Nexus Repository: >> >> https://repository.apache.org/content/repositories/orgapachenifi-1246 >> >> Git Tag: nifi-2.0.0-M1-RC4 >> Git Commit ID: 99f13a89c1b49624e225e53f91d6ae8f3a2a4ab9 >> GitHub Commit Link: >> >> https://github.com/apache/nifi/commit/99f13a89c1b49624e225e53f91d6ae8f3a2a4ab9 >> >> Checksums of nifi-2.0.0-M1-source-release.zip >> >> SHA256: a0b59a66d2f781608775b286ccb08f26d373c7342bd148f4a86f5f5dac841b47 >> SHA512: >> eec87f959037df8620fe314ab8468aac2bfa0ec146c1ed1eabfff999deb3dbd2d416511bf3d8f32aa9f5e7b9343817d5ff08e9784febba7f87e29ea493e4fa6b >> >> 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: 948 >> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599 >> >> Release note highlights can be found on the project wiki: >> >> >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1 >> >> 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-M1 >> [] +0 no opinion >> [] -1 Do not release this package because... >> >
Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC4)
-1 (non-binding) Thank you David for handling the release! - Verified binary hashes and signatures - Successfully built NiFi with contrib-check using: - Apache Maven 3.6.3 - Java 21 2023-09-19 LTS - Ubuntu 22.04 6.2.0-36-generic - Ran some simple flows successfully - Tested minifi-c2 server successfully with MiNiFi C++ (using a draft of the change conforming the new header requirements https://issues.apache.org/jira/browse/MINIFICPP-2244) One issue I encountered: Built a docker image using the nifi-docker/dockerhub/Dockerfile dockerfile and the binaries provided at https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M1/ but the NiFi startup failed with the following error: "Failed to communicate with Python Controller". The PythonBridge class may have some dependency that is missing from the docker image for handling the python processors. As this issue may block the release of the new docker image on Docker Hub it may be worth investigating before releasing this version. Best Regards, Gabor On Mon, 20 Nov 2023 at 18:01, David Handermann wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M1. > > 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-M1 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1246 > > Git Tag: nifi-2.0.0-M1-RC4 > Git Commit ID: 99f13a89c1b49624e225e53f91d6ae8f3a2a4ab9 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/99f13a89c1b49624e225e53f91d6ae8f3a2a4ab9 > > Checksums of nifi-2.0.0-M1-source-release.zip > > SHA256: a0b59a66d2f781608775b286ccb08f26d373c7342bd148f4a86f5f5dac841b47 > SHA512: > eec87f959037df8620fe314ab8468aac2bfa0ec146c1ed1eabfff999deb3dbd2d416511bf3d8f32aa9f5e7b9343817d5ff08e9784febba7f87e29ea493e4fa6b > > 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: 948 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1 > > 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-M1 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.15.0
+1 (non-binding) Went through the verification process using the helper guide. Compiled all but the JNI extension successfully on Ubuntu 22.04 with GCC 11, ran all unit and integration tests, did not find any issues. Compiled on Windows using MSVC and Ninja using Visual Studio 2019. Used the following command: win_build_vs.bat build /NINJA /P /K /S /A /SFTP /PDH /SPLUNK /GCP /ELASTIC /Z /PR /ENCRYPT_CONFIG /MQTT /OPC /PYTHON_SCRIPTING I had a compilation issue on Windows with the SFTP extension: linking SFTPLoader.cpp.obj failed with unresolved Curl symbols. Seems to be an issue of the static linkage of Curl, which is worth investigating, but I don't think it's a blocking issue. After removing SFTP from the compilation list the project compiled successfully. Ran two flows on both Windows (using the compiled binaries) and Linux (using the provided convenience binaries) successfully: TailFile -> LogAttribute GenerateFlowFile -> UpdateAttribute -> MergeContent -> CompressContent -> PutS3Object Note: Updated the https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139627733 wiki page with the new OpenSSL build requirements on Windows. Thanks, Gábor On Tue, 29 Aug 2023 at 23:05, Marton Szasz wrote: > > +1 (binding) > > Verified everything according to the release helper guide. > > On linux, bootstrap.sh installs all the required dependencies for > compiling with GCC. > - Ubuntu 22.04 / GCC: works fine > Clang required additional packages: clang libc++-dev libc++abi-dev > - Ubuntu 22.04 / Clang + libc++: didn't compile, but this is not a > showstopper IMO. We can fix it later and prepare the next release a > bit sooner. > - Ubuntu 22.04 / Clang + libstdc++: works fine > > Arch Linux / any compiler: linker issues related to curl. I wouldn't > tank the release for this. > > Windows steps: > 1. Used Visual Studio Community 2019 (VS2022 support is under review, > not yet included) > 2. Installed scoop (in powershell):> irm get.scoop.sh | iex > 3. Installed the latest cmake (for build), python (for scripting > support), sccache (for build caching, like ccache) and wixtoolset (for > installer generation) with scoop:> scoop install cmake python sccache > wixtoolset > 4. Source checked out at C:\a\m (to avoid long path issues) > 5. Built in "x64 Native Tools Command Prompt for VS2019" with the > following command:> win_build_vs.bat ..\bld /64 /P /K /S /A /SFTP /PDH > /SPLUNK /GCP /ELASTIC /Z /PR /ENCRYPT_CONFIG /MQTT /OPC > /PYTHON_SCRIPTING /D /NONFREEUCRT /SCCACHE > 6. Installed the resulting MSI, and copied cwel_config.yml from the > repo, but modified it to send the logs with PutTCP and PutUDP (2 > separate tests) to a netcat listening on a linux box. It worked well, > the logs arrived right away on the other box. Also tried the new saved > log file support. > > My reaction to Ferenc's issues: > - I agree that we should make 64bit the default in the future. > - I also ran into the cpack issue in the past, but we have a note > about it in the README, which is good enough for now IMO. > - I prefer not starting the service right after installation, before I > even have the chance to add my flow to config.yml, but C2 users may > have different preferences. > > Thanks, > Márton > > > > > > > On Tue, Aug 29, 2023 at 3:20 PM Ferenc Gerlits wrote: > > > > +1 (non-binding) > > > > Verified hashes and signature on the source tarball, checked git > > commit hash and tag. > > Built on Windows 10 with 64-bit VS 2019, installed the msi package and > > ran a simple CWEL -> LogAttribute flow. > > > > I ran into some issues during the build, but none of them are showstoppers: > > - the release helper guide should make it clear that win_build_vs.bat > > defaults to 32-bit and you have to > > add /64 to the command line if you want a 64-bit build (should we > > make 64-bit the default?); > > - win_build_vs.bat fails if the build directory path contains spaces; > > - the cpack command in win_build_vs.bat found chocolatey on my > > computer instead of CMake's cpack; > > - the installer does not start the service (I don't know if it used > > to, but I think it should). > > > > Thank you, > > Ferenc
Re: [DISCUSS] MiNiFi C++ 0.15.0 release
+1 On Thu, 24 Aug 2023 at 17:15, David Handermann wrote: > > +1 > > On Thu, Aug 24, 2023 at 10:14 AM Marton Szasz wrote: > > > > +1. I'm not aware of any blockers. Thanks for taking on RM duties. > > > > On Thu, Aug 24, 2023 at 5:04 PM Joe Witt wrote: > > > > > > +1 a lot of nice things in there! > > > > > > On Thu, Aug 24, 2023 at 7:52 AM Martin Zink wrote: > > > > > > > Hi community, > > > > > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. > > > > The > > > > last release was more than four months ago, and there have been many new > > > > features, bug fixes and stability improvements committed to the > > > > development > > > > branch > > > > since then: 71 tickets closed, over 96 commits as of today. > > > > > > > > I would be happy to take on RM duties for this release. > > > > > > > > Notable features and improvements since the 0.14.0 release: > > > > > > > > - ConsumeWindowsEventLog can work from log files > > > > - ConsumeWindowsEventLog resolve Security/UserID attribute > > > > - TLS v1.3 support > > > > - PutS3Object multipart upload support > > > > - Use systemd service management on Linux > > > > - Add ProcessContext::getStateManager to Lua/Python > > > > - Reworked GetTCP to be more inline with ListenTCP > > > > - SSL support for Prometheus reporter > > > > - Documentation improvements > > > > - Multiarch docker support > > > > - RFC3339 parsing with expression language > > > > - Reworked Minifi controller > > > > - gcc-13 support > > > > > > > > - Fix for waking up prematurely after processor yields > > > > - Fix system certificate store usage in SSLContextService on Linux > > > > - Fix inconsistent naming in C2 machineArch > > > > - Fix default CA path for S3 on CentOS > > > > - Removed CronScheduler locale requirements > > > > > > > > We've upgraded our third party dependencies (notable mentions) > > > > - Replaced LibreSSL with OpenSSL 3.1.1 > > > > - Upgraded RocksDB to v8.1.1 > > > > - Upgraded LibCurl to v8.1.0 > > > > - Upgraded CivetWeb to v1.16 > > > > - Upgraded OpenCV to v4.7.0 > > > > - Upgraded GoogleCloud SDK to v2.10.1 > > > > - Upgraded Azure SDK to v12.7.0 > > > > > > > > The core API is still not mature enough to be able to commit to it, so > > > > in line with previous discussions I suggest releasing it as 0.15.0. > > > > > > > > Do you agree it is time for a new release? Are there any blockers that > > > > we > > > > should definitely include in this release? > > > > > > > > Thanks, > > > > Martin > > > >
[ANNOUNCE] Apache NiFi MiNiFi C++ 0.14.0 release
Hello The Apache NiFi team would like to announce the release of Apache NiFi MiNiFi C++ 0.14.0. New features in this release: - Several improvements on repository resource handling - Periodically run RocksDB repository compaction - Add compression options for RocksDB repositories - Add synchronous flow file reloading - Retry failed removals of unused resources - Use Python stable ABI to support all libraries above Python 3.2+ for Python processors - Add ProcessSession::remove to Python and Lua API - Add support for JSON flow configuration format with option to generate JSON schema locally - Add support for reverseDnsLookup in expression language - Fix most issues for ARM64 support - Improve performance of ListFile processor - Add cache SID lookups in ConsumeWindowsEventLog processor - Add default connection size limits of 2000 queue size and 100MB of queue data size - Add support for MQTT 5 - Add failure relationship to SQL processors - Add support for new AWS regions - Add option to select processor metrics with regular expressions - Add the UUID to the end of Processor and Controller Service log lines - Make GetFile path attributes consistent with other processors - Fix leaks and file lock issues on Windows - Fix crashing in python processors MiNiFi—a subproject of Apache NiFi—is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation. Specific goals for the initial thrust of the MiNiFi effort comprise: - Small size and low resource consumption - Central management of agents - Generation of data provenance (full chain of custody of information) - Integration with NiFi for follow-on dataflow management More details on Apache NiFi MiNiFi can be found here: https://nifi.apache.org/minifi The release artifacts can be downloaded from here: https://nifi.apache.org/minifi/download.html Issues closed/resolved for this list can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352617=12321520 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.14.0 Thank you The Apache NiFi team
Re: [RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.14.0
Third time's the charm... Apache NiFi Community, I am pleased to announce that the 0.14.0 release of Apache NiFi MiNiFi C++ passes with 3 +1 (binding) votes *3 +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: https://lists.apache.org/thread/pqgorhdvd320jy65mkvfc58cx6o7z4gm P.S. Vote result template typos fixed on MiNiFi wiki page :) On Mon, 17 Apr 2023 at 17:37, Gábor Gyimesi wrote: > Apache NiFi Community, > > I am pleased to announce that the 0.14.0 release of Apache NiFi MiNiFi C++ > passes with > 3 +1 (binding) votes > 3 +1 (binding) votes > 0 0 votes > 0 -1 votes > > Thanks to all who helped make this release possible. > > Here is the PMC vote thread: > https://lists.apache.org/thread/pqgorhdvd320jy65mkvfc58cx6o7z4gm >
[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.14.0
Apache NiFi Community, I am pleased to announce that the 0.14.0 release of Apache NiFi MiNiFi C++ passes with 3 +1 (binding) votes 3 +1 (binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread: https://lists.apache.org/thread/pqgorhdvd320jy65mkvfc58cx6o7z4gm
[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.14.0
Apache NiFi Community, I am pleased to announce that the 0.14.0 release of Apache NiFi MiNiFi C++ passes with 3 +1 (binding) votes 3 -1 (binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread: https://lists.apache.org/thread/pqgorhdvd320jy65mkvfc58cx6o7z4gm
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.14.0
Typo correction: *78 issues were closed/resolved for this release On Wed, 12 Apr 2023 at 16:07, Gábor Gyimesi wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > MiNiFi C++ 0.14.0. > > The source tarball, some binary builds, plus signatures and digests can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.14.0/ > > The Git tag is minifi-cpp-0.14.0-RC1 > The Git commit ID is 976b0a165387250a846d13e22b7084fa7c0fb9d3 > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=976b0a165387250a846d13e22b7084fa7c0fb9d3 > > Checksums of nifi-minifi-cpp-0.14.0-source.tar.gz: > SHA256: 09e4633272c1dedf7d3a67aab2d54e6f1c091dbe16764b466ccd4b981a55c1f2 > SHA512: > e46c1b1b90b67b20069d55bdc0d0632c037e32dafbbb9cf0ddaf8ae141292bae7892c9560ba0e73282f3e8f9afb378083bcb73350cfb8fa2cdf477fbb0084520 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/lordgamez.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 8 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352617=12321520 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.14.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-minifi-cpp-0.14.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
[VOTE] Release Apache NiFi MiNiFi C++ 0.14.0
Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.14.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.14.0/ The Git tag is minifi-cpp-0.14.0-RC1 The Git commit ID is 976b0a165387250a846d13e22b7084fa7c0fb9d3 https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=976b0a165387250a846d13e22b7084fa7c0fb9d3 Checksums of nifi-minifi-cpp-0.14.0-source.tar.gz: SHA256: 09e4633272c1dedf7d3a67aab2d54e6f1c091dbe16764b466ccd4b981a55c1f2 SHA512: e46c1b1b90b67b20069d55bdc0d0632c037e32dafbbb9cf0ddaf8ae141292bae7892c9560ba0e73282f3e8f9afb378083bcb73350cfb8fa2cdf477fbb0084520 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 8 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352617=12321520 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.14.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-minifi-cpp-0.14.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.21.0 (RC2)
+1 (non-binding) Verified signatures and hashes Built NiFi on ubuntu 22.04 Ran a simple flow and a flow integrated with MiNiFi C++ through InvokeHTTP LGTM Thanks Joe! BR, Gabor On Thu, 6 Apr 2023 at 14:15, Martin Zink wrote: > +1 (non-binding) > > Went through the helper guide verified signatures and hashes. > I've also verified that integration with the latest MiNiFi C++ works as > expected (InvokeHTTP based flows) > > Everything looks good > > Thanks Joe for RMing! > > On Thu, Apr 6, 2023 at 9:47 AM Ferenc Kis wrote: > > > +1 (non-binding) > > > > - Went through the helper guide, full clean build with contrib check, > > verified signatures and hashes > > Maven home: /Users/fkis/.sdkman/candidates/maven/current > > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > > /Users/fkis/.sdkman/candidates/java/11.0.18-tem > > Default locale: en_HU, platform encoding: UTF-8 > > OS name: "mac os x", version: "13.2.1", arch: "aarch64", family: "mac" > > - Started NiFi, created a simple flow with ListenHTTP > > - Started Nifi Registry, set up integration with NiFi, and saved the > > previous flow to NiFi Registry > > - Started MiNiFi Java: > > * created a simple GenerateFlowFile -> InvokeHttp flow and pushed to > > MiNiFi via C2 protocol > > * managed to push data from MiNiFi to NiFi > > > > Thanks Joe for RMing! > > > > Regards > > Ferenc > > > > On Thu, Apr 6, 2023 at 9:06 AM Pierre Villard < > pierre.villard...@gmail.com > > > > > wrote: > > > > > +1 binding > > > > > > Went through the usual steps. Deployed a 3 node secured cluster on GCP > > with > > > a secure NiFi Registry. Tested some flows. All good. > > > > > > Thanks Joe for taking care of the release! > > > > > > Le jeu. 6 avr. 2023 à 05:11, Mark Bean a > écrit : > > > > > > > +1 (non-binding) > > > > > > > > Verified signatures and hashes. > > > > Performed full build with -Pcontrib-check using maven 3.6.3 and Java > > > > 11.0.18 on Ubuntu 20.04.1. > > > > Installed and ran NiFi again using Java 11.0.18. Executed some basic > > > flows. > > > > > > > > > > > > On Mon, Apr 3, 2023 at 8:11 PM Joe Witt wrote: > > > > > > > > > Hello, > > > > > > > > > > I am pleased to be calling this vote for the source release of > Apache > > > > > NiFi 1.21.0. > > > > > > > > > > The source zip, including signatures, digests, etc. can be found > at: > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1226 > > > > > > > > > > The source being voted upon and the convenience binaries can be > found > > > at: > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.21.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-1.21.0-RC2 > > > > > The Git commit ID is 892f822107da84ca0dcfefdb5c91c5bc11dc3dc1 > > > > > > > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=892f822107da84ca0dcfefdb5c91c5bc11dc3dc1 > > > > > > > > > > Checksums of nifi-1.21.0-source-release.zip: > > > > > SHA256: > > > 598bf8e90f871f4ca25709dd4ecf3da16c814c08c0d8b2c8744dbd34df34dea5 > > > > > SHA512: > > > > > > > > > > > > > > > 58c10976bc22fb5406d9d1d9b7ca7d90c2dbed99565d00f1172bb33b375e9e068da5003d9dbbd87d2b17626e4e310b999c8581718532934e855c2134be763f04 > > > > > > > > > > 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 > > > > > > > > > > 126 issues were closed/resolved for this release: > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352899 > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.21.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-1.21.0 > > > > > [ ] +0 no opinion > > > > > [ ] -1 Do not release this package because... > > > > > > > > > > > > > > >
[DISCUSS] MiNiFi C++ 0.14.0 release
Hi community, I'd like to initiate a discussion about the next release of MiNiFi C++. The last release was almost four months ago, and there have been many new features, bug fixes and stability improvements committed to the development branch since then: 74 tickets closed, over 80 commits as of today. I would be happy to take on RM duties for this release. Notable features and improvements since the 0.14.0 release: - Several improvements on repository resource handling * Periodically run RocksDB repository compaction * Add compression options for RocksDB repositories * Add synchronous flow file reloading * Retry failed removals of unused resources - Use Python stable ABI to support all libraries above Python 3.2+ for Python processors - Add ProcessSession::remove to Python and Lua API - Add support for JSON flow configuration format with option to generate JSON schema locally - Add support for reverseDnsLookup in expression language - Fix most issues for ARM64 support - Improve performance of ListFile processor - Add cache SID lookups in ConsumeWindowsEventLog processor - Add default connection size limits of 2000 queue size and 100MB of queue data size - Add support for MQTT 5 (mistakenly advertised for 0.13.0 release) - Add failure relationship to SQL processors - Add support for new AWS regions - Add option to select processor metrics with regular expressions - Add the UUID to the end of Processor and Controller Service log lines - Make GetFile path attributes consistent with other processors - Fix leaks and file lock issues on Windows - Fix crashing in python processors The core API is still not mature enough to be able to commit to it, so in line with previous discussions I suggest releasing it as 0.14.0. Do you agree it is time for a new release? Are there any blockers that we should definitely include in this release? Thanks, Gabor
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.13.0 (RC2)
+1 (non-binding) - Verified that binaries are no longer in the source archive - Verified signature, hashes and git commit hash - Built RC2 core and all extensions (excluding Tensorflow) with GCC 11.3 on Ubuntu 22.04 - Ran all unit, integration and docker system tests - Verified contents of README.md, NOTICE, and LICENSE files - Verified built binary with simple flows having TailFile, PutFile, GenerateFlowFile, LogAttribute processors and communication through InvokeHTTP processor with NiFi's ListenHTTP processor - Verified Prometheus metrics reporting with built binary and Prometheus 2.35.0 Thanks, Gabor On Mon, 5 Dec 2022 at 15:00, Ferenc Gerlits wrote: > On Mon, Dec 5, 2022 at 2:29 PM John McGinn wrote: > > > Just a note, but the issues closed/resolved list is inaccessible to the > > public. Not sure if it is meant to be that way or not. > > > > The release notes link right below it is accessible though. > > > > Thanks for raising this! It seems to be some weirdness in Jira. We may > have to use the simpler "tickets closed in this release" page: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12351771 > in future release emails -- that one seems to be accessible by anonymous > users. > > Thanks, > Ferenc >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.13.0 (RC1)
+1 (non-binding) - verified signature and hashes of source tar.gz file - verified git commit hash - built RC core and all extensions (excluding Tensorflow) with GCC 11.3 on Ubuntu 22.04 - ran all unit, integration and docker system tests - verified contents of README.md, NOTICE, and LICENSE files - verified https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/nifi-minifi-cpp-0.13.0-bin-linux.tar.gz binary with simple flows having TailFile, GetFile, LogAttribute processors and communication through InvokeHTTP processor with NiFi's ListenHTTP processor - verified Prometheus metrics reporting with built binary and Prometheus 2.35.0 Thanks, Gabor On Wed, 30 Nov 2022 at 11:58, Ferenc Gerlits wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > MiNiFi C++ 0.13.0. > > The source tarball, the binary build, plus signatures and digests can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/ > > The Git tag is minifi-cpp-0.13.0-RC1 > The Git commit ID is 4389b9ac05e43e1dbf908e9014787d07c8a9cd05 > > https://github.com/apache/nifi-minifi-cpp/commit/4389b9ac05e43e1dbf908e9014787d07c8a9cd05 > > Checksums of nifi-minifi-cpp-0.13.0-source.tar.gz: > SHA256: 9cbc37cb841dbd2b53412ded7ba59cd571181b659f647b9d35c3f3ac985337c1 > SHA512: > > 3a69ef1894e4fdc2b2e4d7cd77f46debd86c52a70cfd1a7a76445ae976cfe12bd176cfad3a6aacda2a01aa2ff5810faf2e3d3a8e8ff0de5e460ae19f63db > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/fgerlits.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 85 issues were closed/resolved for this release: > https://issues.apache.org/jira/projects/MINIFICPP/versions/12351771 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.13.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-minifi-cpp-0.13.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.16.3 (RC1)
+1 (non-binding) - Verified signature and hashes - Verified git commit - Built the project on Ubuntu 20.04 and ran a simple flow Regards, Gabor On Tue, 14 Jun 2022 at 06:39, Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.16.3. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1205 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.3/ > > 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.3-RC1 > The Git commit ID is e15bdd7e3d09047d5fed70117b7c3dfd26f3a36e > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=e15bdd7e3d09047d5fed70117b7c3dfd26f3a36e > > Checksums of nifi-1.16.3-source-release.zip: > SHA256: c18edf739361246fe22bb4c2e5a4b1936b6199512b78638868f99b1d827b4d9e > SHA512: > > e3c9942737a0c2cf43fb3030da3cbee7d6be17038f0cf683c9522db25eb6d8664884594d5a7ce2183733568c06b9ccb52c3a6bf6d5ddcb334d2f84477cc68177 > > 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 > > 13 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351844 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.3 > > The vote will be open for 24 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.3 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Re: [DISCUSS] MiNiFi C++ 0.12.0 release
+1 On Tue, 17 May 2022 at 11:30, Pierre Villard wrote: > +1 > > Le mar. 17 mai 2022 à 10:02, Ádám Markovics a > écrit : > > > Hi, > > I also think it's time for a new release. > > Regards, > > > > Ádám > > > > On Mon, May 16, 2022 at 5:32 PM Marton Szasz wrote: > > > > > I agree that it's time for a new release, thanks for RM'ing Martin. > > > > > > I have these two issues that I think would be nice to include in the > > > release: > > > 1. MINIFICPP-1828 fix InvokeHTTP Attributes to Send > > > https://github.com/apache/nifi-minifi-cpp/pull/1331 > > > This is a bug that is severe enough that I would prefer to wait for > > > the fix to get merged before the release. > > > 2. MINIFICPP-1744: Add FetchGCSObject, DeleteGCSObject, ListGCSBucket > > > https://github.com/apache/nifi-minifi-cpp/pull/1297 > > > This would be a nice addition to complete the GCS extension. Not > > > necessarily required for the release, but nice to have IMO. I'll try > > > to post a second review today or tomorrow. > > > > > > > > > > > > On Mon, 16 May 2022 at 14:57, Arpad Boda wrote: > > > > > > > > +1 > > > > > > > > On Mon, May 16, 2022 at 4:12 PM Joe Witt wrote: > > > > > > > > > Certainly more than enough there! Thanks Martin > > > > > > > > > > On Mon, May 16, 2022 at 7:06 AM Martin Zink > > > > wrote: > > > > > > > > > > > Hi community, > > > > > > > > > > > > I'd like to initiate a discussion about the next release of > MiNiFi > > > C++. > > > > > The > > > > > > last release was five months ago, and there have been many new > > > features, > > > > > > bug fixes and stability improvements committed to the development > > > branch > > > > > > since. (~110 commits) > > > > > > I would be happy to take on RM duties for this release. > > > > > > > > > > > > New features since the 0.11.0 release: > > > > > > - new processors: > > > > > >* DeleteAzureBlobStorage > > > > > >* FetchAzureBlobStorage > > > > > >* FetchAzureDataLakeStorage > > > > > >* ListAzureBlobStorage > > > > > >* ListAzureDataLakeStorage > > > > > >* PutGCSObject > > > > > >* ProcFsMonitor > > > > > >* PutUDP > > > > > >* FetchFile > > > > > >* ListFile > > > > > >* PutSplunkHTTP > > > > > >* QuerySplunkIndexingStatus > > > > > > > > > > > > - Log collection from Kubernetes > > > > > > - improved support for Lua processors > > > > > > - platform independent ListenSyslog > > > > > > - property update over C2 protocol > > > > > > > > > > > > The core API is still not mature enough to be able to commit to > it, > > > so > > > > > > in line with previous discussions I suggest releasing it as > 0.12.0. > > > > > > > > > > > > Do you agree it is time for a new release? Are there any blockers > > > that we > > > > > > should definitely include in this release? > > > > > > > > > > > > Thanks, > > > > > > Martin > > > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.11.0 RC2
+1 (non-binding) - verified hashes and signatures - built MiNiFi with all extensions except Tensorflow - executed all unit and integration tests - ran flow file configurations from examples directory with tailing, get-put and S3 flows (getfile_putfile_config.yml, puts3_config.yml, tailfile_config.yml) - set up C2 connection and published a simple flow Thanks, Gabor On Tue, 7 Dec 2021 at 11:48, Pierre Villard wrote: > +1 binding > > Went through the usual steps, built sources and tested a simple flow. > > Le mar. 7 déc. 2021 à 10:53, Ferenc Gerlits a écrit > : > > > +1 (non-binding) > > > > - checked signatures and hashes > > - compared the source to the tag in the repo > > - connected to C2 using TLS > > - ran a simple GetFile -> HashContent -> LogAttribute flow > > > > Everything worked as expected. > > > > Thanks, > > Ferenc > > >
Re: [DISCUSS] MiNiFi C++ 0.11.0 release
Sounds good to me as well! Thanks, Gabor On Thu, 18 Nov 2021 at 15:27, Ferenc Gerlits wrote: > Yes, it's definitely time for a new release, and 0.11.0 sounds good. > Thanks for RMing! > > Ferenc > > > On Wed, Nov 17, 2021 at 12:09 PM Marton Szasz wrote: > > > I agree that it's time for a new release, thank you for taking the RM > > duties. I'm not aware of any blockers at the moment. > > > > Thanks, > > Marton > > > > On Wed, 17 Nov 2021 at 10:28, Adam Debreceni > > wrote: > > > > > > Hi community, > > > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. > > The > > > last release was five months ago, and there have been many new > features, > > > bug fixes and stability improvements committed to the development > branch > > > since. > > > I would be happy to take on RM duties for this release. > > > > > > New features since the 0.10.0 release: > > > - new processors: > > >* AttributesToJson > > >* DefragmentText > > >* PutAzureDataLakeStorage > > >* ReplaceText > > >* RouteText > > > - support for funnels > > > - shared rocksdb repository > > > - repository encryption (flow-file, content) > > > - support for Azure managed identity > > > - modularization of extensions > > > - ConsumeKafka security protocol > > > - platform independent AppendHostInfo > > > - agent configuration checksum in the c2 heartbeat > > > > > > We now use C++17 throughout the codebase and C++20 wherever possible. > > > > > > The core API is still not mature enough to be able to commit to it, so > > > in line with previous discussions I suggest releasing it as 0.11.0. > > > > > > Do you agree it is time for a new release? Are there any blockers that > > we > > > should definitely include in this release? > > > > > > Thanks, > > > Adam > > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ (RC2)
+1 (non-binding) Verified checksums and signatures. Built on Ubuntu 20.04 with all extensions except Tensorflow. Ran unit, integration and docker tests. Tested a simple flow with C2 server. Also built on Windows 10 using VS2017 with tests. Thanks, Gabor On Wed, 9 Jun 2021 at 16:25, Arpad Boda wrote: > +1 (binding) > > Verified build and signatures on Debian 10 and Windows 10. > Executed tests, designed a simple flow and started the agent. > > On Wed, Jun 9, 2021 at 1:20 PM Marton Szasz wrote: > > > +1 (non-binding) > > > > Followed the release helper guide on linux amd64. Verified the build > > and the resulting binaries with both GCC 11 and Clang 12. The flow was > > testing the new ConsumeJournald. > > > > Thanks > > > > On Wed, 9 Jun 2021 at 11:12, Martin Zink > > wrote: > > > > > > +1 (non-binding) > > > > > > Built on windows 10 with MSVC 19.28.29337 and tested the new > > PerformanceDataMonitor processor with a simple flow > > > Also built on linux and tested the new ConsumeJournald processor with a > > simple flow > > > > > > Works as expected, great job! > > > > > > Thank you, > > > Martin > > > > > > ‐‐‐ Original Message ‐‐‐ > > > > > > On Wednesday, June 9th, 2021 at 12:41, Adam Debreceni < > > adebrec...@apache.org> wrote: > > > > > > > +1 (non-binding) > > > > > > > > Verified hashes, signature, commit. Built on macOS with everything > > enabled > > > > > > > > (bootstrap.h -e) ran all tests. > > > > > > > > Built on Windows (/K /PDH /A /64 /2019) ran all tests, deployed > > > > > > > > CWEL->LogAttribute flow through c2 protocol. > > > > > > > > Thank you, > > > > > > > > Adam > > > > > > > > On Mon, Jun 7, 2021 at 9:50 PM Ferenc Gerlits fgerl...@apache.org > > wrote: > > > > > > > > > Hello, > > > > > > > > > > I am pleased to be calling this vote for the source release of > > Apache NiFi > > > > > > > > > > MiNiFi C++ 0.10.0. > > > > > > > > > > The source tarball, some binary builds, plus signatures and digests > > can be > > > > > > > > > > found at: > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.10.0/ > > > > > > > > > > The Git tag is minifi-cpp-0.10.0-RC2 > > > > > > > > > > The Git commit ID is 60d5bc70b567fa7c6689f313a75be17fe7c94080 > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=60d5bc70b567fa7c6689f313a75be17fe7c94080 > > > > > > > > > > Checksums of nifi-minifi-cpp-0.10.0-source.tar.gz: > > > > > > > > > > SHA256: > > f7dc86ef6e35ea0d9c9c39891ea281a9851b1e6fc382b16d3a5931814f5ebc22 > > > > > > > > > > SHA512: > > > > > > > > > > > > > 484d3196d087e7c1acb5d703b827929edf0d8dae295878e1f79232ab8de4fd358f12fa223201c92e0cd9e0c59f2314da9001ac12eb91eabeda751e5d46c4f6b7 > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > > > https://people.apache.org/keys/committer/fgerlits.asc > > > > > > > > > > KEYS file available here: > > > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > 67 issues were closed/resolved for this release: > > > > > > > > > > > https://issues.apache.org/jira/projects/MINIFICPP/versions/12349956 > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.10.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-minifi-cpp-0.10.0 > > > > > > > > > > [ ] +0 no opinion > > > > > > > > > > [ ] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.9.0 (RC1)
+1 (non-binding) Verified checksums and signature. Built on Ubuntu 20.04 with Kafka, Coap, SFTP and AWS extensions. Executed tests. Tested a simple flow with C2 server. BR, Gabor On Tue, 16 Feb 2021 at 23:54, Arpad Boda wrote: > +1 (binding) > > Verified hashes and signature. > Built and executed tests both on Debian 10 and Win 10. > Started agent, connected to C2 server, designed simple flow. > > Cheers, > Arpad > > On Tue, Feb 16, 2021 at 4:57 PM Ferenc Gerlits > wrote: > > > +1 (non-binding) > > > > Verified hashes and the signature on the source bundle. Suggestion: the > > format of the hash file could be changed to " *" so one > > can run eg. 'sha256 -c ...'. > > Built on (a Docker container running) Ubuntu 20.04, enabling everything > > except > > * TensorFlow, because I could not find an Ubuntu package for > libtensorflow; > > * and JNI -- this built without error, but then I had to disable it > because > > it caused a runtime error at startup. I don't think this is a > showstopper. > > Ran the binary using a simple InvokeHTTP -> LogAttribute flow yaml > config; > > it worked as expected. > > > > Thanks, > > Ferenc > > > > On Tue, Feb 16, 2021 at 4:23 PM Adam Debreceni > > wrote: > > > > > +1 (non-binding) > > > > > > Verified checksums and signatures. > > > Built on Windows 10 with kafka. Can connect to c2 server and receive > > > updates. > > > Can process windows event logs in various JSON formats and send them to > > > kafka > > > through SSL, in a multi broker setup. > > > > > > On Tue, Feb 16, 2021 at 9:50 AM Marton Szasz > wrote: > > > > > > > Hello, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > > NiFi MiNiFi C++ 0.9.0 > > > > > > > > The source tarball, including signatures, digests, etc. can be found > > at: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.9.0/ > > > > > > > > The Git tag is minifi-cpp-0.9.0 > > > > The Git commit ID is a52faa5136031abfcc321a44fbcd954ee0f73764 > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=a52faa5136031abfcc321a44fbcd954ee0f73764 > > > > > > > > Checksums of nifi-minifi-cpp-0.9.0-source.tar.gz: > > > > SHA256: > > 40fa837c86707e3bf0e8f0aca5bc279d813205cd326edf809e7785af7282 > > > > SHA512: > > > > > > > > > > 43490ba823d7846c3cc323a634d756a0a33828f5c82a623d19b77c4ddfe3248aa524245ee2c47a7fd04f41c3611758972307e221fa0a254e0aa5831c4f9b03f2 > > > > > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/szaszm.asc > > > > > > > > KEYS file available here: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > 200 issues were closed/resolved for this release: > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12345444 > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.9.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-minifi-cpp-0.9.0 > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > > > >
Require access to MiNiFi confluence page
Hi, I am a contributor to the Apache MiNiFi project currently working on an additional pause-resume feature on the C2 protocol. I would like to update the C2 protocol documentation with this feature on the page https://cwiki.apache.org/confluence/display/MINIFI/C2+Design for which I would like to ask access to with the username lordgamez. BR, Gabor
