You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Andrew Lim (JIRA)" <ji...@apache.org> on 2018/02/09 15:53:01 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16358583#comment-16358583 ] 

Andrew Lim commented on NIFIREG-133:
------------------------------------

Will likely document this in the NiFi User Guide.  If so, will open a separate Jira in NiFi project.  Am in the process of gathering use cases for a Flow Deployment Guide.  Variables in versioned process groups would be a good section for that new document.

> [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
>            Assignee: Andrew Lim
>            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)