[
https://issues.apache.org/jira/browse/NIFI-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157235#comment-15157235
]
Oleg Zhurakousky commented on NIFI-1522:
----------------------------------------
Michael
I am going to strongly disagree with your -1 ;)
Historically 'milliseconds' have been used in programming (many languages) as
the way to describe things like _timeouts, delays and intervals_. All we are
saying now is that while NiFi does provide an ability to *qualify* the meaning
of the number with standard English shorthand, exposing "spoken" language to
describe something that will be used programmatically may lead to variety of
surprises, especially once we start addressing localization of labels etc,
(something that has already been done in some forks) where one may assume that
if labels support "a language" then qualifiers of time expression do too, and
then we start getting things like "1 секунда" or "1秒". So this proposal simply
says, that if "qualification" is not provided (only number is used), then treat
this number as milliseconds. Then we can also describe that you can further
qualify using standard English shorthand such as "sec", "millis" etc., thus
removing ambiguity.
> Period and Unit time expressions should default to milliseconds
> ---------------------------------------------------------------
>
> Key: NIFI-1522
> URL: https://issues.apache.org/jira/browse/NIFI-1522
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Witt
> Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Discussion on Github about our current support for period and unit
> expressions for time
> https://github.com/apache/nifi/pull/210#discussion_r53167209
> We should support that if a unit of time is not specified that the period is
> assumed to be in milliseconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
