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

ASF GitHub Bot commented on NIFI-1464:
--------------------------------------

Github user joewitt commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/210#discussion_r53165063
  
    --- Diff: 
nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java
 ---
    @@ -71,6 +71,7 @@
         public static final String ADMINISTRATIVE_YIELD_DURATION = 
"nifi.administrative.yield.duration";
         public static final String PERSISTENT_STATE_DIRECTORY = 
"nifi.persistent.state.directory";
         public static final String BORED_YIELD_DURATION = 
"nifi.bored.yield.duration";
    +    public static final String PROCESSOR_START_TIMEOUT = 
"nifi.processor.start.timeout";
    --- End diff --
    
    regarding user friendliness the issue we saw before providing a utility for 
more natural expression of duration is that people were very inconsistent in 
specifying the unit of time that a given value applied to and using at times 
periods which didn't make sense for the scenario.  This model allows the user 
to express in a much more natural way both the period of time and unit of time.


> Refactor lifecycle code for Processors and other components
> -----------------------------------------------------------
>
>                 Key: NIFI-1464
>                 URL: https://issues.apache.org/jira/browse/NIFI-1464
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>             Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to