You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Adam Debreceni (Jira)" <ji...@apache.org> on 2020/08/04 13:33:00 UTC

[jira] [Updated] (MINIFICPP-1317) Batch send flowFiles with InvokeHTTP

     [ https://issues.apache.org/jira/browse/MINIFICPP-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Debreceni updated MINIFICPP-1317:
--------------------------------------
    Description: Currently in order to send multiple flowFiles at once through InvokeHTTP a MergeContent processor is used. Unfortunately MergeContent incurs an IO penalty as each merge-result is written to disk. To combat this, we should either make InvokeHTTP capable of sending multiple flowFiles at once, or allow the MergeContent processor to create lazily merged results, where we only store the fact of merger but not the actual result, which is generated on the fly when read.  (was: Currently in order to send multiple flowFiles at once through InvokeHTTP a MergeContent processor is used. Unfortunately MergeContent incurs an IO penalty as each merge-result is written to disk. To combat this, we should either make InvokeHTTP capable of sending multiple flowFiles at once, or allow the MergeContent processor to create lazily merged results, where we only store the fact of merger but not the actual results, which is generated on the fly when read.)

> Batch send flowFiles with InvokeHTTP
> ------------------------------------
>
>                 Key: MINIFICPP-1317
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1317
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Adam Debreceni
>            Assignee: Adam Debreceni
>            Priority: Major
>
> Currently in order to send multiple flowFiles at once through InvokeHTTP a MergeContent processor is used. Unfortunately MergeContent incurs an IO penalty as each merge-result is written to disk. To combat this, we should either make InvokeHTTP capable of sending multiple flowFiles at once, or allow the MergeContent processor to create lazily merged results, where we only store the fact of merger but not the actual result, which is generated on the fly when read.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)