[
https://issues.apache.org/jira/browse/NIFI-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-982:
-----------------------------
Description:
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.
Also noticed that if you make the Maximum number of Bins 1 the behavior is not
consistent and Minimum Number of Entries and Max Bin Age are ignored.
was:
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.
Also noticed that if you make the Maximum number of Bins 1 the behavior is not
consistent and Minimum Number of Entries and Max Bin Age are ignored.
You are also not allowed to set the Header, Footer, and Demarcator to an empty
value or you will get null pointer exceptions.
> Merge Content issues
> --------------------
>
> Key: NIFI-982
> URL: https://issues.apache.org/jira/browse/NIFI-982
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.3.0
> Reporter: Edgardo Vega
> Assignee: Joseph Witt
> Fix For: 0.5.0
>
>
> 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.
> Also noticed that if you make the Maximum number of Bins 1 the behavior is
> not consistent and Minimum Number of Entries and Max Bin Age are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
