[
https://issues.apache.org/jira/browse/NIFI-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913807#comment-17913807
]
ASF subversion and git services commented on NIFI-14166:
--------------------------------------------------------
Commit 2115d68ae7729857d823cb49f8180c8a9ce4302e in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2115d68ae7 ]
NIFI-14166: Added "Bin Termination Check" property to MergeContent; updated
documentation to include the new property and more clearly explain when bins
get merged.
Signed-off-by: Pierre Villard <[email protected]>
This closes #9639.
> Add a "Bin Termination Check" to MergeContent
> ---------------------------------------------
>
> Key: NIFI-14166
> URL: https://issues.apache.org/jira/browse/NIFI-14166
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> MergeContent allows specifying the min and max size of a Bin, which is
> typically what we want in order to create reasonably sized bins. However,
> there are times when we have data that necessitates that we stop binning data
> together and create a new bin, because even though the correlation attribute
> is the same, the incoming FlowFile cannot be added to the existing bin. This
> is especially the case when FIFO prioritizers are used and the ordering of
> the data matters.
> To accommodate this, we can add a new "Bin Termination Check" property. If a
> FlowFile causes the check to return a value of {{{}true{}}}, we should merge
> the bin and start a new one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
