[
https://issues.apache.org/jira/browse/NIFIREG-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454346#comment-16454346
]
Rahul Soni commented on NIFIREG-164:
------------------------------------
Hi [~pvillard]
I agree with your description of what should be identified as a local change.
Identifying a change in value as a local change will result in "Flow out of
sync" issue when a variable value is changed in higher environments.
Closing this issue.
Thanks!
Rahul Soni
> Addition of a new Processor Group Variable not identified as "Local change"
> ---------------------------------------------------------------------------
>
> Key: NIFIREG-164
> URL: https://issues.apache.org/jira/browse/NIFIREG-164
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Rahul Soni
> Priority: Major
>
> Addition of a new Processor Group variable is not identified as "Local
> Change" in NiFi 1.5.0 with NiFi Registry 0.1.0.
> Follows the description and issue reproduction steps.
> # Create a processor group.
> # Add some processors to the Processor Group
> # Start version control
> # Commit the flow to a new bucket
> # Add a new variable to the processor group. This will not be identified as
> a "Local change"
> # Change the position of a processor from your processor group. This will be
> identified as "Local change"
> # "Show local changes" will display only "Position changed for the
> processor" as the change
> # Import the Processor group from the registry to some other canvas.
> # The variable can be seen there.
> So while committing, the variable is not identified as a change but is
> actually written to the registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)