nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-4192) Issue with the MergeContent Processor when processing Avro files
Date Wed, 09 Aug 2017 10:56:00 GMT

    [ https://issues.apache.org/jira/browse/NIFI-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119714#comment-16119714
] 

ASF subversion and git services commented on NIFI-4192:
-------------------------------------------------------

Commit 9c4fdd4ef3589d64e4e15822fc9fdb79a2315535 in nifi's branch refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=9c4fdd4 ]

NIFI-4192: Add more Avro/metadata merge options to MergeContent

Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes #2067.


> Issue with the MergeContent Processor when processing Avro files
> ----------------------------------------------------------------
>
>                 Key: NIFI-4192
>                 URL: https://issues.apache.org/jira/browse/NIFI-4192
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>
> Currently the Avro Merge strategy in MergeContent requires that any key/value pairs in
the Avro non-reserved metadata must match. This might have been done to support re-merging
of split Avro files upstream, since the "fragment.*" capability was added afterward.
> Now that the fragment.* attributes are available to help merge a batch of flow files,
the user should be able to select the Avro Metadata Strategy the same way as the Attribute
Strategy, with the additional option of "Ignore if unmatched", which should be default to
maintain currently functionality.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message