[
https://issues.apache.org/jira/browse/NIFI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598633#comment-14598633
]
Mark Payne commented on NIFI-719:
---------------------------------
The MonitorMemory reporting task and potentially others should also make use of
this value instead of looking at the value in the init method, as this can
change from one scheduling of the component to the next.
> For Reporting Tasks, ConfigurationContext should provide scheduling
> information
> --------------------------------------------------------------------------------
>
> Key: NIFI-719
> URL: https://issues.apache.org/jira/browse/NIFI-719
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Fix For: 0.2.0
>
>
> Currently the ConfigurationContext does not provide any information about
> scheduling, as it was originally designed for Controller Services. However,
> it is used also for Reporting Tasks, and should have methods "Long
> getSchedulingPeriod(TimeUnit timeUnit)" and "String getSchedulingPeriod()" as
> the ReportingInitializationContext does. These methods should return null for
> Controller Services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
