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 2018/01/30 20:36:00 UTC
[jira] [Updated] (NIFIREG-133) [Documentation] Explain how
variables are captured when versioning a PG
[ https://issues.apache.org/jira/browse/NIFIREG-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard updated NIFIREG-133:
-----------------------------------
Summary: [Documentation] Explain how variables are captured when versioning a PG (was: [Documentation] Explain how variables are captures when versioning a PG)
> [Documentation] Explain how variables are captured when versioning a PG
> -----------------------------------------------------------------------
>
> Key: NIFIREG-133
> URL: https://issues.apache.org/jira/browse/NIFIREG-133
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Pierre Villard
> Priority: Minor
>
> Context:
> I have a process group PG that contains an embedded process group PG1. I have a variable defined at PG level that is referenced in a PG1's processor. When versioning both PG and PG1 in NiFi Registry, a copy of the variable defined at PG level will be created at PG1 level.
> Consequently, when importing PG in another environment, the variable needs to be modified at PG1 level because the one created at PG1 level overwrites the one initially defined at PG level.
> > Would be nice to add this behavior in the documentation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)