Volker Klasen created NIFI-16278:
------------------------------------

             Summary: NiFi 2.11.0: Inherited Parameters Become Local when 
Adding Inheritance
                 Key: NIFI-16278
                 URL: https://issues.apache.org/jira/browse/NIFI-16278
             Project: Apache NiFi
          Issue Type: Bug
    Affects Versions: 2.11.0
            Reporter: Volker Klasen


Hello,

I already posted [this issue on the mailing 
list|https://lists.apache.org/thread/490ppjxckct3jsq37q2w1wp488xcswm7], but 
wanted to file it now also as ticket.

In NiFi 2.11.0 we're observing a bug that inherited parameters become local 
ones when adding an inheritance. As another effect, when using multiple 
hierarchies sensitive values get set as local parameters with stars as value. 
This was working without issue in 2.10.0.

How to reproduce:
* Create a parameter context named "test" without parameters
* Create a parameter context named "test2" with on parameter
* Edit parameter context "test" to inherit from "test2" and save
* Edit parameter context "test", remove the inheritance from "test2" and save
* Edit "test" again and notice that the parameter from "test2" is still present 
and shown as inherited, while no inheritance is present
* Look into current flow.json and notice that parameter context "test" has the 
parameter from "test2" as local parameter set
* Optional: delete parameter context "test2", log out and in again and notice 
that the parameter context page cannot be opened anymore
* Restart Nifi to fix the "ghostly" inheritance and notice that parameter 
context "test" now has a local parameter

It looks like the issue occurs only when adding an inheritance, existing 
inheritances from before 2.11.0 work as expected.

Workaround for adding parameter contexts in 2.11.0 correctly:
* Add the inheritance you want to have
* Restart NiFi
* Remove the local "copies" of inherited parameters from the child parameter
* Now the context has only the (correctly) inherited parameters (and any other 
local parameters)

This issue might be related to https://issues.apache.org/jira/browse/NIFI-16226 
and maybe caused by https://issues.apache.org/jira/browse/NIFI-16148

Cheers
Volker



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

Reply via email to