[
https://issues.apache.org/jira/browse/NIFIREG-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788298#comment-16788298
]
Bryan Bende commented on NIFIREG-231:
-------------------------------------
[~Max Kelada] I think this is working as expected...
When a new version is committed in NiFi, it captures all of the variable
references and their current values and sends them registry, even if they came
from a parent group.
Once the version is in registry, it has no more knowledge that there was even a
parent group, so I'm not sure what we could indicate here. If this version is
imported to another NiFi instance, it may or may not have a parent group with
that variable.
> NiFi Registry variable registry hierarchy problem
> -------------------------------------------------
>
> Key: NIFIREG-231
> URL: https://issues.apache.org/jira/browse/NIFIREG-231
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Nimrod Avni
> Priority: Major
> Labels: scope, variable-registry
> Attachments: RegistryResponse.PNG, nifiVariableRegistry.PNG
>
>
> We have ran into the where i am building my flow, and i am using variables
> from the variable registry from a scope outside of my current process group.
> as well as variables from the scope of my current process group
> After committing the flow i sent a GET request to :
> <<nifi-registy-url>>/nifi-registry-api/buckets/<<bucket-id>>/flows/<<flow-id>>/versions/<<current-version>>
> when looking inside the flow/flowContents/variables section i saw both
> variables, one from the outer scope of the process group and one from scope
> of the versioned flow with no way to tell them apart, there should be a way
> to tell apart these two variables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
