Mark Payne created NIFI-3521:
--------------------------------
Summary: MergeContent continually complains about not having
enough fragments when configured in Defragment mode
Key: NIFI-3521
URL: https://issues.apache.org/jira/browse/NIFI-3521
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Mark Payne
I have MergeContent configured in defragment mode. I am feeding it the result
of SplitText (after some transformation) and then went to re-assemble the
FlowFiles. MergeContent keeps transferring flowfiles to failure with the
following error:
2017-02-22 16:36:47,584 ERROR [Timer-Driven Process Thread-1]
o.a.n.processors.standard.MergeContent
MergeContent[id=66e56829-015a-1000-dc0b-6d8fcd9b3c71] Cannot Defragment
FlowFiles with Fragment Identifier dadd3357-3253-4c4d-a4cb-9d9b1673789f because
the expected number of fragments is 375 but found only 343 fragments; routing
343 FlowFiles to failure
In defragment mode, it is expected that the FlowFiles may not be all available
initially and should require that a Max Bin Age be set. FlowFiles should be
failed only if the max bin age has been exceeded.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
