[jira] [Resolved] (NIFI-5854) Enhance time unit features

["Matt Burgess (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-5854.
--------------------------------
    Resolution: Fixed

> Enhance time unit features
> --------------------------
>
>                 Key: NIFI-5854
>                 URL: https://issues.apache.org/jira/browse/NIFI-5854
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.8.0
>            Reporter: Andy LoPresto
>            Assignee: Andy LoPresto
>            Priority: Major
>              Labels: parsing, time, units
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is some ambiguity with time units (specifically around processor properties). Two features which I think should be added:
> * Currently only whole numbers are parsed correctly. For example, {{10 milliseconds}} and {{0.010 seconds}} are functionally equivalent, but only the former will be parsed. This is due to the regex used in {{StandardValidators.TIME_PERIOD_VALIDATOR}} which relies on {{FormatUtils.TIME_DURATION_REGEX}} (see below). Decimal amounts should be parsed
> * The enumerated time units are *nanoseconds, milliseconds, seconds, minutes, hours, days, weeks*. While I don't intend to extend this to "millennia", etc. as every unit including and above *months* would be ambiguous, *microseconds* seems like a valid and missing unit
> *Definition of {{FormatUtils.TIME_DURATION_REGEX}}:*
> {code}
>     public static final String TIME_DURATION_REGEX = "(\\d+)\\s*(" + VALID_TIME_UNITS + ")";
>     public static final Pattern TIME_DURATION_PATTERN = Pattern.compile(TIME_DURATION_REGEX);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)