[
https://issues.apache.org/jira/browse/NIFI-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110174#comment-15110174
]
Joseph Witt commented on NIFI-982:
----------------------------------
Just checked into this issue and noticed that the description appears to be for
a different (much older) version of NiFi. Checked 030 codebase as seen in [1]
and it has the correct validator. Verified the latest code and behavior too.
It not only requires you to specify both a duration and unit but it enforces a
min and max range equivalence from 1 second to max integer size seconds.
Tested that too with '1 ms' and that was properly invalidated. In short the
filed issue does not appear to be an issue any longer and this validator was
verified as far back as Jan 2015.
[1]
https://github.com/apache/nifi/blob/nifi-0.3.0-RC1/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/BinFiles.java#L93
> Merge content bin age should support time units
> -----------------------------------------------
>
> Key: NIFI-982
> URL: https://issues.apache.org/jira/browse/NIFI-982
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.3.0
> Reporter: Edgardo Vega
> Assignee: Joseph Witt
>
> In the Merge Content processor the property Max Bin Age does not support the
> other commonly used time units (e.g s, sec). It only supports seconds and
> does not throw a validation error you put in another time unit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
