[
https://issues.apache.org/jira/browse/NIFI-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779401#comment-17779401
]
sky commented on NIFI-12187:
----------------------------
[~mosermw] Hello, the problem I have is that when I have 100 data in the queue
in front of mergecontent, but I set the mergecontent 'Maximum Number of
Records' to 200, When the timer arrives, 'relaxFullnessConstraint &&
bin.isFullEnough()' fails to meet the condition and fails to merge, and then
waits until the data in the queue reaches 200, which is inconsistent with the
business expectation. The business expects to merge when the timer arrives,
regardless of whether the 'Maximum Number of Records' is met.
> MergeContent"relaxFullnessConstraint && bin.isFullEnough() "can never be
> reached.
> ---------------------------------------------------------------------------------
>
> Key: NIFI-12187
> URL: https://issues.apache.org/jira/browse/NIFI-12187
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.16.0, 1.17.0, 1.16.1, 1.16.2, 1.16.3, 1.18.0, 1.19.0,
> 1.20.0, 1.19.1, 1.21.0, 1.22.0, 1.23.0, 1.23.1, 1.23.2
> Reporter: sky
> Priority: Critical
>
> In MergeContent, "binContents.size() < maximumEntries" does not work, but it
> does work in 1.15.3. At that time in the "migrateBins" method of
> "BinFiles.java", "BinManager. RemoveReadyBins (true)" in the subsequent
> version into "binManager. RemoveReadyBins (relaxFullnessConstraint)", As a
> result, "relaxFullnessConstraint && bin.isFullEnough() "can never be achieved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
