[
https://issues.apache.org/jira/browse/NIFI-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680743#comment-17680743
]
ASF subversion and git services commented on NIFI-11089:
--------------------------------------------------------
Commit 7d99521d4cb557d713df4d6dbb56b6b7ccd54cc4 in nifi's branch
refs/heads/main from Joe Gresock
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7d99521d4c ]
NIFI-11089: Resolving previously resolved parameter providers when possible on
version sync (#6886)
> Import from registry can create duplicate parameter providers
> -------------------------------------------------------------
>
> Key: NIFI-11089
> URL: https://issues.apache.org/jira/browse/NIFI-11089
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Joe Gresock
> Priority: Minor
> Fix For: 1.20.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> While testing the fix for NIFI-11039, I created a scenario that created
> duplicate providers when importing from registry, when the intent was for
> them to be the same provider.
> Scenario:
> * Create FileParameterProvider with two directories specified (group1,
> group2)
> * Create parameter contexts from each group
> * Create a flow with parent pg and child pg
> * Configure parent to use group1 context
> * Configure child to use group2 context
> * Save flow to registry
> * Delete everything from nifi (PGs, contexts, provider)
> * Import PG from registry
> Import succeeds because of the issue resolved in NIFI-11039, but note that
> now two instances of FileParameterProvider were created, when the snapshot
> from registry only has one instance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
