[
https://issues.apache.org/jira/browse/NIFI-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597802#comment-14597802
]
ASF subversion and git services commented on NIFI-378:
------------------------------------------------------
Commit e767f5ce02c36f41874d4f97abdb50c643662deb in incubator-nifi's branch
refs/heads/develop from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e767f5c ]
Merge branch 'NIFI-378' into develop
> MergeContent in Defragment mode will merge fragments without checking index
> ---------------------------------------------------------------------------
>
> Key: NIFI-378
> URL: https://issues.apache.org/jira/browse/NIFI-378
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.0.1
> Reporter: Michael Moser
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments:
> 0001-NIFI-378-updated-documentation-to-explain-contract-o.patch
>
>
> When in Defragment mode, the MergeContent processor looks for
> fragment.identifier and fragment.count attributes in order to place FlowFiles
> in the correct bin. The fragment.index attribute is ignored.
> If you happen to have many FlowFile in the queue to MergeContent, and they
> all have fragment.identifier=foo and fragment.count=2, then it will merge two
> FlowFiles that have fragment.index=1 or it will merge two FlowFiles that have
> fragment.index=2.
> Granted this may seem odd. The use case is to give the MergeContent
> processor two input queues. We configure one queue to contain files with
> fragment.index=1 and the other queue to contain files with fragment.index=2.
> We want one file from each queue to be merged. Instead it will merge two
> files from the same queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
