[
https://issues.apache.org/jira/browse/NIFI-13849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-13849:
----------------------------------
Priority: Minor (was: Major)
> Convert property to parameter tries to delete inherited parameters
> ------------------------------------------------------------------
>
> Key: NIFI-13849
> URL: https://issues.apache.org/jira/browse/NIFI-13849
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 2.0.0-M4
> Reporter: Pierre Villard
> Priority: Minor
>
> Steps to reproduce:
> * Create a Parameter Context PCi with parameter A
> * Create a Parameter Context PC that inherits PCi
> * Create a Process Group that uses PC
> * In the process group, create a flow GFF -> InvokeHTTP, configure
> InvokeHTTP to use parameter A, and start InvokeHTTP processor (add a dummy
> endpoint and autoterminate relationships). In GFF, add a dynamic property foo
> => foo. Then click the Convert to Parameter option and click OK.
> At this point it will fail saying that the parameter A cannot be deleted
> because InvokeHTTP is running.
> *Important note: if InvokeHTTP is NOT running, the conversion of the property
> value into a parameter works as expected and nothing gets deleted in the
> inherited parameter contexts.*
> Debugging shows that this is because the ParameterContextDTO object sent in
> the update request specified null for the inherited parameter contexts and it
> makes the current logic think that all of the parameters from inherited
> parameter contexts should be deleted.
> When adding the parameter directly in the parameter context view, the same
> ParameterContextDTO object does correctly reference the inherited parameter
> context.
> It feels like a fix in the UI is needed so that the update request includes
> the references to the inherited parameter contexts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
