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

Alaksiej Ščarbaty updated NIFI-14405:
-------------------------------------
    Description: 
When importing a flow from a Schema registry it's possible to unselect the 
_Keep existing Parameter Contexts_ checkbox to create a new version of the 
Parameter Context and not to use any existing parameter context in NiFi.

When it comes to importing json files in the _Create Process Group_ pop-up the 
existing parameter context is always used. This limitation complicates the 
creation of the same flow multiple times, each with its own parameter 
configuration.

  was:
When importing a flow from a Schema registry it's possible to unselect the 
_Keep existing Parameter Contexts_ checkbox not to use the existing parameter 
contexts in NiFi.

When it comes to importing json files in the _Create Process Group_ pop-up the 
existing parameter context is always used. This limitation complicates the 
creation of the same flow multiple times, each with its own parameter 
configuration.


> Option to create a copy of Parameter Context when importing a json flow
> -----------------------------------------------------------------------
>
>                 Key: NIFI-14405
>                 URL: https://issues.apache.org/jira/browse/NIFI-14405
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Alaksiej Ščarbaty
>            Priority: Major
>
> When importing a flow from a Schema registry it's possible to unselect the 
> _Keep existing Parameter Contexts_ checkbox to create a new version of the 
> Parameter Context and not to use any existing parameter context in NiFi.
> When it comes to importing json files in the _Create Process Group_ pop-up 
> the existing parameter context is always used. This limitation complicates 
> the creation of the same flow multiple times, each with its own parameter 
> configuration.



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

Reply via email to