You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/02/04 12:54:00 UTC
[jira] [Updated] (NIFI-15547) Parameter Provider bundle version fallback not applied during flow import
[ https://issues.apache.org/jira/browse/NIFI-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard updated NIFI-15547:
----------------------------------
Status: Patch Available (was: Open)
> 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: 10m
> 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)