[jira] [Updated] (NIFI-4828) MergeContent only processes one bin even if there are multiple ready bins

["Koji Kawamura (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Kawamura updated NIFI-4828:
--------------------------------
    Status: Patch Available  (was: Open)

> MergeContent only processes one bin even if there are multiple ready bins
> -------------------------------------------------------------------------
>
>                 Key: NIFI-4828
>                 URL: https://issues.apache.org/jira/browse/NIFI-4828
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.0.0
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>            Priority: Major
>         Attachments: mergecontent-multi-bins.xml
>
>
> [BinFiles.processBins|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/bin/BinFiles.java#L219] is expected to loop through all ready bins, but it only process the first bin. This incurs larger latency for FlowFiles to be merged.
> For example, if there are two FlowFiles FF1 and FF2 queued for a MergeContent processor, each has an attribute named 'group'. FF1.group = 'a', and FF2.group = 'b'. MergeContent is configured to use 'Correlation Attribute Name' as 'group'.
> MergeContent takes FF1 and FF2 from its input queue, then correctly creates two bins for group a and b, each having FF1 and FF2 respectively.
> Bug BinFiles.processBins only processes the first bin, which can be either the bin for group a or b. The other bin is left unprocessed.
> The attached flow template has a flow to reproduce this.
> Expected behavior is MergeContent to process all queued FlowFiles at a single onTrigger run.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)