[
https://issues.apache.org/jira/browse/NIFI-16064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098302#comment-18098302
]
ASF subversion and git services commented on NIFI-16064:
--------------------------------------------------------
Commit c7c745e8c8dcc7518b9d03720c85879cf29281be in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c7c745e8c8d ]
NIFI-16064 Preserve local Public Port Names on updates from Version Control
(#11384)
Signed-off-by: David Handermann <[email protected]>
> The name of a remote inputport change name when updating from version control
> -----------------------------------------------------------------------------
>
> Key: NIFI-16064
> URL: https://issues.apache.org/jira/browse/NIFI-16064
> Project: Apache NiFi
> Issue Type: Bug
> Components: Flow Versioning
> Affects Versions: 2.9.0, 2.10.0
> Reporter: Jens M Kofoed
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If you have created a "Generic process group" with a remote input port inside
> which you put in version control. And you reuse this PG multiple places, the
> name of the "Remote Input port" automattacly change to "copy of xxxx". Sinse
> you are not allowed to have 2 remote input ports with the same name. I belive
> that this is also why a change in the name does not consider a "local
> change". Next you change the "copy of xxxx" to something meaningfull - All is
> fine.
> Issue: If you have made other changes to that PG and upload a new version.
> All other PG which is connected to that version-control also need updates.
> Now when you update a PG to the new version the input port change the name
> back to what is defined in the saved version in registry. This is
> unfurtunally an unexpacted behaiver
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
