[
https://issues.apache.org/jira/browse/NIFI-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150539#comment-15150539
]
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_r53167209
--- 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 --
I can see why convention over configuration is strong within a development
community but what we observed across a wide variety of a user community was
very different need.
Regarding what is arguably 'natural' from one language to another this is a
great point that I personally had not considered. Fortunately I believe the
set of supported terms to accept as indicators of periods can be substantially
expanded though I am not aware of how problematic ambiguity could be. We could
of course choose to support some specific standard for expression of time
periods though so still have viable paths.
> 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)
