[jira] [Commented] (NIFI-719) For Reporting Tasks, ConfigurationContext should provide scheduling information

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610492#comment-14610492 ] 

ASF subversion and git services commented on NIFI-719:
------------------------------------------------------

Commit ba3155980efd846b45bd47eefa14f503a13908f3 in incubator-nifi's branch refs/heads/develop from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=ba31559 ]

NIFI-719: Expose scheduling period to the ConfigurationContext


> 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)