You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Charlie Meyer (JIRA)" <ji...@apache.org> on 2019/04/05 21:46:00 UTC
[jira] [Commented] (NIFI-6194) Updating variables does not properly
resolve referencing components causing variable updates to incorrectly fail
[ https://issues.apache.org/jira/browse/NIFI-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811294#comment-16811294 ]
Charlie Meyer commented on NIFI-6194:
-------------------------------------
i just downloaded 1.9.0 and replicated it there as well, so this was not introduced in 1.9.1
> Updating variables does not properly resolve referencing components causing variable updates to incorrectly fail
> ----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6194
> URL: https://issues.apache.org/jira/browse/NIFI-6194
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.9.1
> Reporter: Charlie Meyer
> Priority: Major
> Attachments: nifi_bug.xml
>
>
> steps to reproduce:
>
> There is attached XML template for a flow. It contains:
> * Root PG
> ** variable named {{my_id}} in the variable registry
> ** an updateattribute processor that references {{my_id}}
> ** a nested process group
> *** overrides {{my_id}} in its variable registry
> *** an update attribute processor that references {{my_id}}
> # load the template into a clean nifi
> # start up the 2 updateattribute processors
> # open the root PG's variable registry and attempt to change the value of variable named {{my_id}}
> # itll show only 1 processor references it, which is correct.
> # the update request will incorrectly fail as it resolves the updateattribute processor in the nested processgroup as referencing the {{my_id}} variable in the root pg, even though it is actually referencing the overridden {{my_id}} in the nested PG where it is provisioned
>
> In the update request, the first steps succeed:
> {noformat}
> {"description": "Identifying components affected","complete": true},
> {"description": "Stopping affected Processors","complete": true},{noformat}
> But the {{affectedComponents}} section of the update-request only shows 1 processor which is correct. The {{"Applying Updates"}} step of the update fails and the error message references the uuid of the processor in the nested PG which is referencing the overridden value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)