-1 (binding)

The new version changes the bundle group identifier for all components in the C2 manifest to a hardcoded "componentManifest", which causes issues with C2 servers using the group identifier to identify components. This can break matching controller service types to the types/interfaces expected in processor properties, and potentially causing issues when updating from a previous version, because all components change their identity.

In older versions, this group id used to be "org.apache.nifi.minifi" on all the processors I've checked. This affects both extensions using the new stable API/ABI and extensions using the older build-coupled API. Unfortunately this group id is just outside of the actual "componentManifest" element that we have automated tests for. :(

I think we need to fix this issue before we publish the 1.0 version. Let's discuss offline how to fix it!

Things I've tested:
- the usual hashes, signature, commit id, etc
- building with all extensions enabled on Ubuntu 24.04 with GCC 13
- building on Arch Linux with GCC 16
- building on Fedora Asahi Remix (arm64) with GCC 16
  - when compiling in Debug profile but with -O3, I've ran into some weird issue with static initialization in the rocksdb extension, but this build setup was accidental and not something we need to support, so I think we can ignore this   - when building in normal debug/relwithdebinfo/release mode, things worked perfectly
- running some tests on all of the above
- a flow with Martin's work-in-progress rust processors

Things I didn't test yet:
- strictly following the release helper guide (docker container or clean ubuntu install)
- using the python bootstrap script to set up the build environment
- building on Ubuntu 26.04
- forwarding data to NiFi

Aside from this manifest breakage, everything else I tried worked well. The builds went more smoothly than in previous releases. :)

Thanks,
Marton

On 7/30/26 6:47 PM, Marc Parisi wrote:
+1  (binding ).

I couldn't miss the chance to test things out.

verified sigs and hashes, built on pop os ( linux) . ran tests and executed
a simple flow

Great stuff!

thanks,
marc


On Wed, Jul 29, 2026 at 1:54 PM Gábor Gyimesi <[email protected]> wrote:

+1 (binding)

- Verified hashes, signature, and git commit/tag
- Verified the build of MiNiFi C++ with all extensions on Ubuntu 24.04
and Windows 10
- Ran all unit tests on both system
- Ran all system tests on Ubuntu 24.04
- Designed some simple flows on a C2 server involving Python processors

Everything works as expected!

Thanks for RMing, Martin!

Regards,
Gabor

On Wed, 29 Jul 2026 at 16:53, Martin Zink <[email protected]> wrote:
Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi
MiNiFi C++ 1.0.0.

Please review the following guide for how to verify a release candidate
build:

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303
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/1.0.0/

The Git tag is minifi-cpp-1.0.0-RC1
The Git commit ID is 7b54eb7db84cb020434937ff429945ec9e529bbe

Checksums of nifi-minifi-cpp-1.0.0-source.tar.gz:
SHA256: 624d300e6e33aa5e92a53835bf16c60f37b034295d95f8df77a66f52400947c7
SHA512:

2788f15af51d61d6f4a5c488506096622fc951e42a8b694660c2aa4a1ed92986643e5fd19369c7254fbeba22efd0e08b4608aaef9e8f1b9ed4dba6b41f86db7c
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/martinzink.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

143 issues were closed/resolved for this release:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520
Release note highlights can be found here:

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-1.0.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-1.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Reply via email to