[
https://issues.apache.org/jira/browse/NIFI-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084672#comment-16084672
]
ASF subversion and git services commented on NIFI-4060:
-------------------------------------------------------
Commit b603cb955dcd1d3d9b5e374e5760f2f9b047bda9 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b603cb9 ]
NIFI-4060: Initial implementation of MergeRecord
NIFI-4060: Addressed threading issue with RecordBin being updated after it is
completed; fixed issue that caused mime.type attribute not to be written
properly if all incoming flowfiles already have a different value for that
attribute
NIFI-4060: Bug fixes; improved documentation; added a lot of debug information;
updated StandardProcessSession to produce more accurate logs in case of a
session being committed/rolled back with open input/output streams
Signed-off-by: Matt Burgess <mattyb...@apache.org>
This closes #1958
> Create a MergeRecord Processor
> ------------------------------
>
> Key: NIFI-4060
> URL: https://issues.apache.org/jira/browse/NIFI-4060
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.4.0
>
>
> When record-oriented data is received one record or a time or needs to be
> split into small chunks for one reason or another, it will be helpful to be
> able to combine those records into a single FlowFile that is made up of many
> records for efficiency purposes, or to deliver to downstream systems as
> larger batches. This processor should function similarly to MergeContent but
> make use of Record Readers and Record Writer so that users don't have to deal
> with headers, footers, demarcators, etc.
> The Processor will also need to ensure that records only get merge into the
> same FlowFile if they have compatible schemas.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
