You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Eric Secules (Jira)" <ji...@apache.org> on 2020/04/15 00:42:00 UTC

[jira] [Updated] (NIFI-7363) Deleting/Modifying Parameters with Nifi Registry

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

Eric Secules updated NIFI-7363:
-------------------------------
    Environment: 
NIFIREG 0.5.0
NIFIREG 0.6.0

  was:NIFIREG 0.5.0


> Deleting/Modifying Parameters with Nifi Registry
> ------------------------------------------------
>
>                 Key: NIFI-7363
>                 URL: https://issues.apache.org/jira/browse/NIFI-7363
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.11.1, 1.11.4
>         Environment: NIFIREG 0.5.0
> NIFIREG 0.6.0
>            Reporter: Eric Secules
>            Priority: Major
>
> I am noticing that when I delete a parameter from a parameter context in NiFi a number of strange things result.
>  * It doesn't register as a change that I can commit to the registry
>  * When I do make a change and commit to the registry, the deleted parameter remains there and will be downloaded by anyone downloading the latest version of the flow.
>  * When I look into the registry's file system, at the bottom of the .snapshot files I notice that each individual process group has a listing of parameters and their values each with slight differences from eachother. This is weird because the documentation says that parameter contexts are global so I was expecting a single parameter context entity somewhere.
> What I expect to happen:
>  * When I delete or modify the value of a parameter I should be able to check that in in a versioned way so that newer process group versions see the changes but older versions do not.
>  * I expected that since parameter contexts are independent of process groups, that they would be versioned independently of process groups.
>  
>  I have noticed that the parameter context gets bloated with a bunch of parameters that have no users and no way to delete them after doing a big renaming effort.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)