You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/11/30 14:11:00 UTC
[jira] [Commented] (NIFI-4648) Max Bin Age within MergeContent has
misleading description
[ https://issues.apache.org/jira/browse/NIFI-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272707#comment-16272707 ]
Joseph Witt commented on NIFI-4648:
-----------------------------------
[~nadenf] have you verified there is actually a problem or were you just noticing the code? I ask because that 'asTimePeriod' mechanism takes the underlying string value of say (5 mins) and converts it to the seconds integer necessary. This way a processor can be built against whatever time unit it wants/needs and all the logic is in a single point for interpreting that from what the user supplied.
> Max Bin Age within MergeContent has misleading description
> ----------------------------------------------------------
>
> Key: NIFI-4648
> URL: https://issues.apache.org/jira/browse/NIFI-4648
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.0
> Reporter: Franco
>
> The Max Bin Age attribute within MergeContent has the description as such:
> "The maximum age of a Bin that will trigger a Bin to be complete. Expected format is <duration> <time unit> where <duration> is a positive integer and time unit is one of seconds, minutes, hours"
> Except that it only supports seconds as you can tell here: binManager.setMaxBinAge(context.getProperty(MAX_BIN_AGE).asTimePeriod(TimeUnit.SECONDS).intValue());
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)