[
https://issues.apache.org/jira/browse/NIFI-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056921#comment-18056921
]
ASF subversion and git services commented on NIFI-15547:
--------------------------------------------------------
Commit 89f1d4fef028b9618a0e7e2aabe740ed9db67f94 in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=89f1d4fef0 ]
NIFI-15547 Fixed Parameter Provider compatible version fallback on Import Flow
(#10849)
Signed-off-by: David Handermann <[email protected]>
> Parameter Provider bundle version fallback not applied during flow import
> -------------------------------------------------------------------------
>
> Key: NIFI-15547
> URL: https://issues.apache.org/jira/browse/NIFI-15547
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When importing a flow (via upload, paste, or creating a versioned process
> group) that references a Parameter Provider with a bundle version not
> available in the system, NiFi fails to create the Parameter Provider even
> when only one compatible version is available.
> For processors and controller services, NiFi applies fallback logic via
> discoverCompatibleBundles() to resolve to an available bundle version.
> However, this method was not being called for Parameter Providers during flow
> import operations in ProcessGroupResource.java.
> Impact: Parameter Providers referenced in imported flows are not created when
> their exact bundle version doesn't match, even though the component type is
> available with a different version.
> Fix: Add
> serviceFacade.discoverCompatibleBundles(flowSnapshot.getParameterProviders())
> calls alongside the existing
> discoverCompatibleBundles(flowSnapshot.getFlowContents()) calls in the proper
> code paths.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
