[
https://issues.apache.org/jira/browse/NIFI-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436317#comment-17436317
]
endzeit edited comment on NIFI-9352 at 10/30/21, 2:49 PM:
----------------------------------------------------------
I may be missing something here, but is this an actual incorrect behaviour?
When the schedule is set to run every hour, I personally don't necessarily
expect the processor to run directly, thus essentially more often than every
hour - just because I change a variable it's using.
Is this an actual regression and has been working as described before? Just
asking because I'm wondering if that's the wanted and widely expected
behaviour? I personally would expect a processor to run again, when restarting
it explicitly, but not necessarily when it's stopped and started from an
"outside effect".
was (Author: endzeitbegins):
I may be missing something here, but is this an actual incorrect behaviour?
When the schedule is set to run every hour, I don't necessarily expect the
processor to run directly, thus essentially more often than every hour - just
because I change a variable it's using.
Is this an actual regression and has been working as described before? Just
asking because I'm wondering if that's the wanted and widely expected
behaviour? I personally would expect a processor to run again, when restarting
it explicitly, but not necessarily when it's stopped and started from an
"outside effect".
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
