[
https://issues.apache.org/jira/browse/NIFI-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Van Kerrebroeck updated NIFI-16318:
----------------------------------------
Description:
When getting a flow from registry (gitlab integration) and leaving the "Keep
existing Parameter Contexts" checked, still NiFi tries to change some
parameters.
!image-2026-09-08-14-06-38-786.png|width=530,height=393!
In a previous trial, when no other flows were running, it actually did change
the parameter to the value from the registry. In the example above another flow
was running, so it couldn't change it.
The flow was not imported and the only way to import is to stop the other
existing flow and let it update the parameter... This is dangerous and can
result in wrong processing if parameters change to other values.
Expected behaviour: existing parameters should NEVER be overwritten when the
option is checked.
I've never noticed this behaviour in older nifi versions (v1)
(to be clear: not all parameters are affected. Some are, others not. I guess
it's related to parameter context inheritance)
was:
When getting a flow from registry (gitlab integration) and leaving the "Keep
existing Parameter Contexts" checked, still NiFi tries to change some
parameters.
!image-2026-09-08-14-06-38-786.png|width=530,height=393!
In a previous trial, when no other flows were running, it actually did change
the parameter to the value from the registry. In the example above another flow
was running, so it couldn't change it.
The flow was not imported and the only way to import is to stop the other
existing flow and let it update the parameter... This is dangerous and can
result in wrong processing if parameters change to other values.
Expected behaviour: existing parameters should NEVER be overwritten when the
option is checked.
I've never noticed this behaviour in older nifi versions (v1)
> Import from registry changes existing parameters when not allowed
> -----------------------------------------------------------------
>
> Key: NIFI-16318
> URL: https://issues.apache.org/jira/browse/NIFI-16318
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.11.0
> Environment: OS: RedHat (RedHat 8.10)
> Kernel: 4.18.0
> CPUs: 4 (Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz)
> GitLab integration via the GitLabFlowRegistryClient
> Reporter: Sven Van Kerrebroeck
> Priority: Major
> Attachments: image-2026-09-08-14-06-38-786.png
>
>
> When getting a flow from registry (gitlab integration) and leaving the "Keep
> existing Parameter Contexts" checked, still NiFi tries to change some
> parameters.
> !image-2026-09-08-14-06-38-786.png|width=530,height=393!
> In a previous trial, when no other flows were running, it actually did change
> the parameter to the value from the registry. In the example above another
> flow was running, so it couldn't change it.
> The flow was not imported and the only way to import is to stop the other
> existing flow and let it update the parameter... This is dangerous and can
> result in wrong processing if parameters change to other values.
> Expected behaviour: existing parameters should NEVER be overwritten when the
> option is checked.
> I've never noticed this behaviour in older nifi versions (v1)
> (to be clear: not all parameters are affected. Some are, others not. I guess
> it's related to parameter context inheritance)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
