Matt Gilman created NIFI-16374:
----------------------------------
Summary: After Connector migration, prefix the source Process
Group with "(Decommissioned)" instead of "(Migrated)"
Key: NIFI-16374
URL: https://issues.apache.org/jira/browse/NIFI-16374
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Matt Gilman
Assignee: Matt Gilman
h2. Background
After a successful local Connector migration, NiFi disables the source Process
Group and prefixes its name so it is obvious the group is no longer the live
ingestion path.
Today that prefix is "(Migrated)". That label is misleading: the source group
is not a migrated copy of the flow. It is the original group after it has been
taken out of service. "(Decommissioned)" matches the actual cleanup behavior.
h2. Proposed Change
In StandardConnectorMigrationManager.disableAndRenameSourceProcessGroup, rename
the source Process Group with the prefix "(Decommissioned)" instead of
"(Migrated)".
Idempotency should still skip the rename when the name already starts with
either:
* "(Decommissioned)" (new prefix)
* "(Migrated)" (legacy prefix from earlier migrations)
That avoids stacking prefixes such as "(Decommissioned) (Migrated) My Flow" if
migration cleanup runs again against a previously renamed group.
Existing groups that already have the "(Migrated)" prefix do not need to be
rewritten in place. Only newly finalized migrations should get the new prefix.
h2. Documentation / Tests
* Update the Administration Guide "Cleanup after a successful migration"
section.
* Update unit tests in TestStandardConnectorMigrationManager.
* Update system test assertions in AbstractConnectorVersionedFlowMigrationIT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
