awelless opened a new pull request, #11813: URL: https://github.com/apache/nifi/pull/11813
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You under the Apache License, Version 2.0 --> <!-- (the "License"); you may not use this file except in compliance with --> <!-- the License. You may obtain a copy of the License at --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --> <!-- See the License for the specific language governing permissions and --> <!-- limitations under the License. --> # Summary [NIFI-16310](https://issues.apache.org/jira/browse/NIFI-16310) In this PR migration-created services are assigned a versioned component id on creation. The version id is derived from an enclosing process group. - If the process group is a top level versioned group, flow identifier is used. - Otherwise a group’s versioned id is used. We can’t use creator (processor/service) versioned id, as multiple creators can use a single controller service. In that case the service’s versioned id will depend on which component creates se service, so the id wouldn’t be deterministic. If no group identifier is available, a controller service is kept unversioned. However, it is not removed during synchronization. ## Codee changes `StandardControllerServiceFactory` now accepts `owningGroupIdentity` to derive a versioned id from it. This identity is resolved and set by`StandardVersionedComponentSynchronizer`. `VersionedFlowSynchronizer` provides no identity - it's responsible for synchronizing "Controller settings" components, which aren't a part of any versioned process group. ### Verification - Synchronizer unit tests. - Controller service factory unit tests. - System tests. ### Additional changes `FileSystemFlowRegistryClient` which is used in system tests was moved into a separate NAR, to be available before and after NAR swap. ## Suggested review order - `MigrationCreatedControllerServiceVersioningIT` and its dependencies to see the relevant use cases. - `StandardControllerServiceFactory` and `StandardVersionedComponentSynchronizer` for actual implementation. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` - Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status ### Pull Request Formatting - Pull Request based on current revision of the `main` branch - Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `./mvnw clean install -P contrib-check` - [x] JDK 21 - [ ] JDK 25 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
