[
https://issues.apache.org/jira/browse/NIFI-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859711#comment-16859711
]
ASF subversion and git services commented on NIFI-6349:
-------------------------------------------------------
Commit 99350b761dda3458757563b633ed21e5524257d4 in nifi's branch
refs/heads/master from Evan Reynolds
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=99350b7 ]
NIFI-6349 Fix to MergeRecords when handling fragments over multiple iterations
Fixed fragment count attribute check
This closes #3517.
Signed-off-by: Koji Kawamura <[email protected]>
> MergeRecord does not merge fragmented files correctly
> -----------------------------------------------------
>
> Key: NIFI-6349
> URL: https://issues.apache.org/jira/browse/NIFI-6349
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.9.2
> Reporter: Evan Reynolds
> Priority: Major
> Labels: pull-request-available
> Attachments: Merge_Test_Flow.xml
>
> Original Estimate: 24h
> Time Spent: 1h 20m
> Remaining Estimate: 22h 40m
>
> When MergeRecords tries to merge fragments it will close the bin after a
> single run. This means that fragments that come in seconds apart will not be
> merged.
> To replicate this, import the attached flow template and run the
> GenerateFlowFile processor. It will generate 2000 flow files. MergeRecord
> should merge them back but a number of them will fail.
> To replicate this in a unit test, go to the testDefragment method and change
> "runner.run(1)" to "runner.run(2)". It will fail.
> In code - it is using the minimum number of records, which defaults to 1, to
> see if the bin is full. Once a single fragment comes in, the bin will show
> full and will be marked complete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
