[jira] [Closed] (NIFIREG-164) Addition of a new Processor Group Variable not identified as "Local change"

["Rahul Soni (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFIREG-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rahul Soni closed NIFIREG-164.
------------------------------
    Resolution: Not A Bug

Report problem has been identified as "Not a bug". Please see comments section for more details. 

Closing.

> 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)