[
https://issues.apache.org/jira/browse/NIFI-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157272#comment-15157272
]
Joseph Witt commented on NIFI-1522:
-----------------------------------
[~mosermw] Just want to be sure I understand what you are in favor of.
Are you stating you believe that at all times whenever expression duration
both the period and unit should be explicitly specified and the unit should
never be assumed?
Of course I share that tendency because that is how it was designed thus far
and I think it is correct to have this approach for a user/operator
perspective. Where I can see Oleg's point is that for many developers knowing
a default unit is often sufficient. I believe we can address both concerns
through user experience. By that I mean I think if the user enters only a time
period we automatically enter in a unit of time as well which would default to
'ms'. With such an approach we're always making it explicit. I think this is
only feasible in the UI/REST API. For nifi.properties I think we need it to
actually be explicit always because we don't want to have the application
changing what the user enters there.
> 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)
