[ 
https://issues.apache.org/jira/browse/NIFI-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684031#comment-17684031
 ] 

ASF subversion and git services commented on NIFI-11118:
--------------------------------------------------------

Commit 28b9f6fc020616ac5d1f99a2477fe456458560a8 in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=28b9f6fc02 ]

NIFI-11118: This closes #6909. When changing version of a versioned flow, 
ensure that we properly set the Version Control Information's StorageLocation 
for the NiFi Registry client in order to maintain backward compatibility

Signed-off-by: Joe Witt <[email protected]>


> Show Local Modifications shows all changes in child group after changing 
> version
> --------------------------------------------------------------------------------
>
>                 Key: NIFI-11118
>                 URL: https://issues.apache.org/jira/browse/NIFI-11118
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.20.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> To replicate:
>  # Create a Process Group named Parent
>  # In that Process Group, create a new Process Group named Child
>  # In Child, add an Input Port, a Processor such as UpdateAttribute, and an 
> Output Port. Connect them together.
>  # In Parent, create a GenerateFlowFile and connect it to the Child input port
>  # Version Control Child
>  # Version Control Parent
>  # Move the UpdateAttribute Processor in Child. Save next Version
>  # Move UpdateAttribute again. Save next Version
>  # Save version of Parent
>  # Remove Connection from GenerateFlowFile to Child Input Port
>  # Change Child from Version 3 to Version 1
>  # Change Child from Version 1 to Version 3
>  # View Local Modifications in Parent. We should see only that the connection 
> was removed, but it's showing all components in the child group as newly 
> added.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to