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.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to