You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "marco polo (JIRA)" <ji...@apache.org> on 2017/06/13 20:25:00 UTC

[jira] [Commented] (MINIFI-322) Create MergeContent processor

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

marco polo commented on MINIFI-322:
-----------------------------------

I'm going to do this in stages. It will not be feature complete per the Java Variant. Is there anything specific you think would be useful [~randerzander]

> Create MergeContent processor
> -----------------------------
>
>                 Key: MINIFI-322
>                 URL: https://issues.apache.org/jira/browse/MINIFI-322
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++, Extensions
>            Reporter: Randy Gelhausen
>            Assignee: marco polo
>
> http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.MergeContent/index.html
> A primary use case for MiNiFi is flow management of high volume data at the edge of networks. Today, the S2S protocol provides compression for multiple flowfiles but this does not provide sufficient control over prioritization, rates, and sizes.
> The addition of the MergeContent processor would provide significantly more end-user customization of how and when MiNiFi ships data to NiFi and other systems.



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