You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2025/09/24 15:12:00 UTC
[jira] [Updated] (NIFI-15011) FlowDifferenceFilters - handle splitRelationship()
[ https://issues.apache.org/jira/browse/NIFI-15011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard updated NIFI-15011:
----------------------------------
Status: Patch Available (was: Open)
> FlowDifferenceFilters - handle splitRelationship()
> ---------------------------------------------------
>
> Key: NIFI-15011
> URL: https://issues.apache.org/jira/browse/NIFI-15011
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> Consider something like:
>
> {code:java}
> @Override
> public void migrateRelationships(final RelationshipConfiguration config) {
> if (!config.hasRelationship(B)) {
> config.splitRelationship(A.getName(), A.getName(), B.getName());
> }
> super.migrateRelationships(config);
> }{code}
> Then I'd see a local change such as:
> Selected Relationships Changed - From '[A]' to '[A, B]'
>
> If the relation B didn't exist at all in the flow definition, and if the source processor does not support dynamic relationships, then this change should not show as a local change.
> Similarly, if the processor does not support dynamic relationships and if we have:
> {code:java}
> @Override
> public void migrateRelationships(final RelationshipConfiguration config) {
> if (!config.hasRelationship(A)) {
> config.splitRelationship(OLD.getName(), A.getName(), B.getName());
> }
> super.migrateRelationships(config);
> }{code}
> (we remove an OLD relationship that we split into two new ones)
> We should not show a local change like:
> Selected Relationships Changed - From '[OLD]' to '[A, B]'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)