[
https://issues.apache.org/jira/browse/NIFI-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436312#comment-17436312
]
Mark Payne commented on NIFI-9352:
----------------------------------
Of note, this issue was identified because the ProcessGroupVariablesIT system
test fails. Is another good way to verify the fix.
> Components that reference variable in user-defined property are not
> stopped/restarted when variable is updated
> --------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-9352
> URL: https://issues.apache.org/jira/browse/NIFI-9352
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.15.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.15.0
>
>
> When a Process Group's variable is updated, any component that references
> that variable must first be stopped and then restarted. However, if a
> processor references the variable in a user-defined property, it does not get
> stopped & restarted.
> To illustrate:
> - Create a GenerateFlowFile processor
> - Add a user-defined property if "Hello" with a value of "${greeting}"
> - Create a variable named "greeting" in the Process Group and give it any
> value - say "hello".
> - Connect GenerateFlowFile to an UpdateAttribute and set the Run Schedule to
> "1 hour".
> - Start GenerateFlowFile. It should run once.
> - Update variable to have a value of "good-bye".
> - After changes have been applied, you should have seen GenerateFlowFile run
> twice - once with a value of "hello" and again with a value of "good-bye" but
> currently you'll see it have only run once.
> As a result, when a variable is change, it may not take effect on all
> processors until restart of NiFi.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
