[
https://issues.apache.org/jira/browse/NIFI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599726#comment-14599726
]
Matt Gilman commented on NIFI-719:
----------------------------------
Much better :)
The scheduling issues observed in MonitorMemory have been resolved with this
patch.
+1
> 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
> Assignee: Mark Payne
> Fix For: 0.2.0
>
> Attachments:
> 0001-NIFI-719-Expose-scheduling-period-to-the-Configurati.patch
>
>
> 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)
