Thanks Pierre. I can confirm that your PR fixes the issue, but:
1. I can't judge if other NIP-21 discussion participants would like the
new structure, so I'm hesitant to +1 your PR.
2. I see another (seemingly unrelated) issue pop up with API 2.7.0 when
building NiFi git main with it:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.14.1:compile
(default-compile) on project nifi-web-api: Compilation failure:
Compilation failure:
[ERROR]
/home/szaszm/verify-nifi-release/work/nifi_repo/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java:[4094,27]
error: the switch expression does not cover all possible input values
[ERROR]
/home/szaszm/verify-nifi-release/work/nifi_repo/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java:[6439,27]
error: the switch expression does not cover all possible input values
The problem is that the ComponentType enum got a new value CONNECTOR,
and now switch blocks that don't handle that case no longer compile. I'm
not confident enough around NiFi to know the exact backwards
compatibility guarantees we provide, but treating new public enum values
as a breaking change seems a bit too restrictive.
Let's discuss these and save the work of another RC. :)
Thanks,
Marton
On 3/6/26 10:15 AM, Pierre Villard wrote:
-1, I just love doing RCs :)
Thanks to Marton for reporting an issue with JAXB. I submitted a fix for it [1].
The TL;DR is that the NiFi Registry framework includes a
FlowContentSerializer that supports multiple data model versions for
reading stored flow snapshots. Data model version 1 uses a JAXB-based
serializer (it's probably something that should go away...) and it has
some limitations (it can't handle interfaces).
[1] https://github.com/apache/nifi-api/pull/76
Thanks,
Pierre
Le jeu. 5 mars 2026 à 21:02, Pierre Villard
<[email protected]> a écrit :
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi API 2.7.0.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification+for+NiFi+API
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-api-2.7.0
The build artifacts are available on the Apache Nexus Repository:
https://repository.apache.org
Git Tag: nifi-api-2.7.0-RC3
Git Commit ID: 83b33d7fe57fbcc359516266c978459366166faf
GitHub Commit Link:
https://github.com/apache/nifi-api/commit/83b33d7fe57fbcc359516266c978459366166faf
Hashes of nifi-api-2.7.0-source-release.zip
SHA512:
b89b0231f430de99d19915eafb494aafdb7e1b5c1ee500d8ad4a2ff768171eb243b68d3c55af08c5a966d70ac2a0a6d0de519c35df23abe2cb7ef099b569aeb6
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/pvillard31.asc
KEYS file is available on the Apache Distribution Repository:
https://dist.apache.org/repos/dist/release/nifi/KEYS
Issues resolved for this version: 14
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12356655
Release note highlights can be found on the project wiki:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiAPIVersion2.7.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-api-2.7.0
[] +0 no opinion
[] -1 Do not release this package because...
