[
https://issues.apache.org/jira/browse/NIFI-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225483#comment-17225483
]
Joe Witt commented on NIFI-7975:
--------------------------------
I'll add if you're values are as follows:
min entries: 1
min size: 0 MB
max entries: 100
max size: 100 MB
max age: 60 secs
Then after the first run, even if there is just a single flowfile, it will
produce a merge result. If there are many flowfiles in queue ready to go it
will grab as many as it can in that run. <it can require more thought if you
decide to run mergecontent in parallel but lets ignore that for now>
If you want instead for it to really focus on efficient bin packing (near max
size) then make your minimums close to your maximum's and set the max age.
> MergeContent closes almost empty bins
> -------------------------------------
>
> Key: NIFI-7975
> URL: https://issues.apache.org/jira/browse/NIFI-7975
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.9.2
> Reporter: Jiri Meluzin
> Priority: Major
> Attachments: BinPackingAlgorithmDoc.png
>
>
> In case of Bin-Packing Algorithm Merge Strategy the MergeContent processors
> marks bins as processed even if bin contains only 1 flow-file.
> Expected behavior would be that MergeContent waits for other flow-files so
> the bin contains Maximum Number of Entries as it is documented at the
> strategy - see BinPackingAlgorithmDoc.png
> It is prety easy to reproduce - just use one GenerateFlowFile processor with
> Run Schedule set to 1 sec and connect it with MergeContent processor with
> default settings. Then run it and MergeContent processor produces same numbed
> of Merged flow-files as the GenerateFlowFile.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
