[
https://issues.apache.org/jira/browse/NIFI-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225482#comment-17225482
]
Joe Witt commented on NIFI-7975:
--------------------------------
The language in that tooltip could be improved to make it clear that bins are
made consistent with the rest of the properties of the processor. But you need
to review the properties of MergeContent as shown in
http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.12.1/org.apache.nifi.processors.standard.MergeContent/index.html
Minimum number of entries AND minimum size of those entries must be reached and
if so we'll make a bin within this run....
If not then...
Maximum entires must be reached --OR-- maximum size those entries represent
must be reached and if so then we'll make a bin with this run....
IF none of the above happens then we will check whether the things we're
putting together have been in progress of binning for 'max bin age' and if so
then we'll merge/send forward regardless of above terms.
This is how it works. This processor is fairly complex but it is also
extremely powerful and incredibly popular in use.
I'm going to resolve this as information provided. If you believe the above is
NOT true/not happening and you can verify that on 1.12.x then we can revisit.
> 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)
