[
https://issues.apache.org/jira/browse/NIFI-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Secules updated NIFI-7363:
-------------------------------
Affects Version/s: 1.11.4
Description:
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.
was:
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 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.
I am working on confirming this with the latest releases of NiFi and registry,
but from reading the release notes it doesn't look like any improvements have
been released to parameter contexts.
> 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
> 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)
