[
https://issues.apache.org/jira/browse/NIFI-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434137#comment-16434137
]
ASF GitHub Bot commented on NIFI-5074:
--------------------------------------
GitHub user andrewmlim opened a pull request:
https://github.com/apache/nifi/pull/2627
NIFI-5074 Added section Variables in Versioned Flows to User Guide
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewmlim/nifi NIFI-5074
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2627.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2627
----
commit a758765555f3b353caa56bd83f4198ac1be0dd32
Author: Andrew Lim <andrewlim.apache@...>
Date: 2018-04-11T16:24:16Z
NIFI-5074 Added section Variables in Versioned Flows to User Guide
----
> Add section to User Guide explaining how variables are captured when
> versioning a PG
> ------------------------------------------------------------------------------------
>
> Key: NIFI-5074
> URL: https://issues.apache.org/jira/browse/NIFI-5074
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Reporter: Andrew Lim
> Assignee: Andrew Lim
> Priority: Minor
>
> Issue originally filed as NIFIREG-133. Filing in NIFI project since addition
> will be made to the NiFi User Guide.
> Original Jira description:
> 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)
