[NIFI-4192] Issue with the MergeContent Processor when processing Avro files

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 17/Jul/17 13:33
• Updated: 09/Aug/17 10:56
• Resolved: 09/Aug/17 10:56

Description

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.

Issue Links

• links to: GitHub Pull Request #2067