[
https://issues.apache.org/jira/browse/NIFI-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111761#comment-18111761
]
Eric Secules commented on NIFI-16276:
-------------------------------------
I have also found a workaround. If a ProcessGroup is stored in version control
even with an empty parameter context, you will no longer loose the actual
assigned parameter context when upgrading the versions of instances of your
shared process group.
> Parameter context is removed from process group after upgrading from version
> control
> ------------------------------------------------------------------------------------
>
> Key: NIFI-16276
> URL: https://issues.apache.org/jira/browse/NIFI-16276
> Project: Apache NiFi
> Issue Type: Bug
> Components: Flow Versioning
> Affects Versions: 2.9.0, 2.11.0
> Reporter: Jens M Kofoed
> Assignee: Eric Secules
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a process group are put in version control without a parameter context.
> But are used with a parameter context set directly on the PG, an update to a
> new version will remove the paramter context again.
> There are cases where a shared PG could be used many places, and reference to
> paramters which are set in a parameter context for the parent pg instead of a
> paramter context associated directly with the shared PG. Therefore the PG
> didn't have a paramter context when put in version control. But a parameter
> context are applied to the PG when it is used.
> But when updateing to a newer version, since the version control says there
> are no parameter context, the update process removes the paramter context
> which was set in the used place
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
