You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Jiri Meluzin (Jira)" <ji...@apache.org> on 2020/11/03 15:00:00 UTC

[jira] [Created] (NIFI-7975) MergeContent closes almost empty bins

Jiri Meluzin created NIFI-7975:
----------------------------------

             Summary: 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
         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)