[
https://issues.apache.org/jira/browse/NIFI-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573969#comment-14573969
]
Joseph Witt commented on NIFI-379:
----------------------------------
The bug appears to have been just an improper handling for edge testing.
Should have been '<=' but was just <. This bug was most 'obvious' in the case
of a single bin but it would also impact the efficiency of packing bins
whenever the max number of bins is reached for any reason.
I am not entirely sure the logic for 'migrateBins' of BinFiles which kicks out
the oldest bin whenever the max bins is reached and no bins are ready to be
processed is correct. But can't quite reason over it enough to flag it so
moving on.
> MergeContent does not merge when Maximum number of Bins is set to 1
> -------------------------------------------------------------------
>
> Key: NIFI-379
> URL: https://issues.apache.org/jira/browse/NIFI-379
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.0.1
> Reporter: Michael Moser
> Assignee: Joseph Witt
> Fix For: 0.2.0
>
>
> Set the Maximum number of Bins property of the MergeContent processor to 1.
> The merged output always contains 1 file, no matter what the other settings
> are.
> Might be best to prevent the user setting Maximum number of Bins to 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
