[
https://issues.apache.org/jira/browse/NIFI-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354555#comment-16354555
]
ASF GitHub Bot commented on NIFI-4816:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2452
The idea for storing off the name for all reporting tasks is to support
#2431 , in fact that's where this behavior was discovered.
I like the @OnScheduled setName() idea, I may call it something more
specific (rather than a bean method) since it will take a context. Will make
the change, thanks!
> Changes to ReportingTask name are not available to the ReportingTask
> --------------------------------------------------------------------
>
> Key: NIFI-4816
> URL: https://issues.apache.org/jira/browse/NIFI-4816
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> The Reporting Task name is only set on the ReportingTask itself during
> initialize(), which is only called the first time the ReportingTask is
> instantiated. This means if you change the name of the ReportingTask and
> restart it, The ReportingTask has its original name and the current name is
> inaccessible via the ConfigurationContext it is passed later. If you restart
> NiFi, the new name is set and stays that way.
> Rather than calling initialize() more than once, it is proposed to make the
> current name (and any other appropriate properties) available perhaps via
> ConfigurationContext which is passed to methods annotated with OnScheduled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
