[ 
https://issues.apache.org/jira/browse/NIFI-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003808#comment-18003808
 ] 

ASF subversion and git services commented on NIFI-14717:
--------------------------------------------------------

Commit 1a37c9ff9a363dc276a5d3936ae3cbca899571b0 in nifi's branch 
refs/heads/main from Dominik
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1a37c9ff9a ]

NIFI-14717 Updated MergeContent to create a Bin when Max Bin Age reached 
(#10068)

- Updated MergeContent to create a Bin when Max Bin Age reached regardless of 
whether there are new FlowFiles also queued

Signed-off-by: David Handermann <[email protected]>

> MergeContent Processor should release a bin when maxBinAge condition is 
> fulfilled
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-14717
>                 URL: https://issues.apache.org/jira/browse/NIFI-14717
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 2.4.0
>            Reporter: Dominik Bartos
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The `MergeContent` processor currently releases a bin when its age exceeds 
> the `Max Bin Age` property value _and_ there are no new FlowFiles upstream. 
> However, the bin should be released regardless of the second condition.
> Current behaviour is unacceptable for clients whose flows process continuous 
> stream data e.g. database CDC stream. MergeContent should not rely on the 
> pace of producing FlowFiles by an upstream.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to