[
https://issues.apache.org/jira/browse/NIFI-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626432#comment-16626432
]
ASF subversion and git services commented on NIFI-5514:
-------------------------------------------------------
Commit 2a964681eca443cc335b6f269d2b9ddab57250c7 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2a96468 ]
NIFI-5514: Fixed bugs in MergeRecord around minimum thresholds not being
honored and validation not being performed to ensure that minimum threshold is
smaller than max threshold (would previously allow min record = 100, max
records = 2 as a valid configuration)
NIFI-5514: Do not rely on ProcessSession.getQueueSize() to return a queue size
of 0 objects because if the processor is holding onto data, the queue size
won't be 0.
Signed-off-by: Pierre Villard <[email protected]>
This closes #2954.
> MergeRecord does not create a merged FlowFile until a maximum threshold is
> reached
> ----------------------------------------------------------------------------------
>
> Key: NIFI-5514
> URL: https://issues.apache.org/jira/browse/NIFI-5514
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.8.0
>
>
> MergeRecord allows the user to specify a minimum number of records. However,
> if the minimum number of records is reached, the merged FlowFile is not
> created unless the maximum number of records or max number of bytes is also
> reached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
