[jira] [Updated] (NIFI-4192) Issue with the MergeContent Processor when processing Avro files
[ https://issues.apache.org/jira/browse/NIFI-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4192: - Component/s: Extensions > 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 > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess > Fix For: 1.4.0 > > > 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)
[jira] [Updated] (NIFI-4192) Issue with the MergeContent Processor when processing Avro files
[ https://issues.apache.org/jira/browse/NIFI-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4192: - Resolution: Fixed Fix Version/s: 1.4.0 Status: Resolved (was: Patch Available) > 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 > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess > Fix For: 1.4.0 > > > 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)
[jira] [Updated] (NIFI-4192) Issue with the MergeContent Processor when processing Avro files
[ https://issues.apache.org/jira/browse/NIFI-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-4192: --- Status: Patch Available (was: In Progress) > 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)
