Chris, Thanks for raising this question for discussion.
Summarizing similar comments on Slack, this does not seem like a Release Candidate concern, but it is worth adding a note to the Migration Guidance page. The automated property migration capabilities support transparent handling of existing flow configurations when upgrading NiFi versions. This allows things like renaming properties, removing properties, and replacing properties with Controller Services in some scenarios. Having addressed some edge case scenarios in recent versions, this functionality has remained largely unchanged for the NiFi 2 release series. That being said, the automated migration does not account for creating new Processors or Controller Services with old property names, using the Toolkit or the REST API. This means that it is necessary for the calling client to understand the current state of property names and send the correct names according to the current version of the Component in question. One way to handle this is evaluating the NiFi version and sending the expected names. This does introduce some manual work, or version checking, for installations that use programmatic component creation, but it is effectively the same operation as creating a new component through the UI. The component manifest documentation might be one source to evaluate potential differences. With that background, this could be an area for further improvement, but for now, it seems like the migrate properties capability is working as designed. Regards, David Handermann On Sun, Dec 7, 2025 at 3:46 PM Chris Sampson <[email protected]> wrote: > > [DISCUSS] test results > > I ran through the release helper on a Mac (Tahoe 26.1) with openjdk version > "25.0.1" 2025-10-21 LTS. > > I additionally built the Container Images locally using Docker (Maven -P > docker profile) and tested the resulting images using a docker compose > stack containing NiFi, NiFi Registry, and calls through the NiFi Toolkit to > create various components and Flows for testing. > > In general this worked well, but I noted that Reporting Tasks and global) > Controller Services created via the Toolkit do not have their Properties > migrated, e.g. "record-writer" is not migrated to "Record Writer" for any > of the Site-to-Site Reporting Tasks. Similarly the "key-password" is not > migrated to "Key Password" for StandardSSLControllerServices. Note also, > that in the latter case, the (should be sensitive) value of the invalid > key-password is printed to the UI tooltip warning, leading to potential > secret exposure. > > Reported in Slack to the #dev channel [1] for discussion. > > I'm not sure whether this meets the threshold for a negative vote, although > this would technically be a breaking change for anyone creating such > components via the NiFi API (e.g. with Toolkit), so may warrant further > investigation before release. > > > [1]: https://apachenifi.slack.com/archives/C0L9S92JY/p1765138020254559 > > > Cheers, > > --- > *Chris Sampson* > Principal Software Engineer > Naimuri > > > On Sat, 6 Dec 2025 at 20:35, Pierre Villard <[email protected]> > wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 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 > > > > 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.7.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1324 > > > > Git Tag: nifi-2.7.0-RC4 > > Git Commit ID: 46e83d2aea47dd4285a667f7fdb93b40bb1198c3 > > GitHub Commit Link: > > > > https://github.com/apache/nifi/commit/46e83d2aea47dd4285a667f7fdb93b40bb1198c3 > > > > Hash of nifi-2.7.0-source-release.zip > > > > SHA512: > > > > bf1f5fd0e5ecedcbd8eb8d82df9e56b1f4564492ede659e61d20fd03e5aaf3503a720d8061c706f05a74141aaee2836889c73404dfd284f53070fc8052671b75 > > > > 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: 268 > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12356272 > > > > Release note highlights can be found on the project wiki: > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.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-2.7.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > >
