[jira] [Commented] (NIFI-7505) Add InvokeHTTPRecord processor

["Alessandro D'Armiento (Jira)" <ji...@apache.org>]

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

Alessandro D'Armiento commented on NIFI-7505:
---------------------------------------------

Do you think such a Processor should also emit a different FlowFile for each record (as each different invocation could succeed or fail independently) acting in a similar way than SplitRecord? 

As per the main behaviour, I guess this processor should be able to add the record content to the request body (or parameters in case of GET)

What do you think?

> Add InvokeHTTPRecord processor
> ------------------------------
>
>                 Key: NIFI-7505
>                 URL: https://issues.apache.org/jira/browse/NIFI-7505
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.11.4
>            Reporter: Andy LoPresto
>            Priority: Major
>              Labels: Record, http, processor, rest
>
> Some users have recently requested being able to invoke a specific URL via {{InvokeHTTP}} on every record in a flowfile. Currently, the {{InvokeHTTP}} processor can only handle one piece of data per flowfile. There are some workarounds available for specific patterns with {{LookupRecord}} + {{RestLookupService}}, but this is not a complete solution. I propose introducing an {{InvokeHTTPRecord}} processor, providing the {{InvokeHTTP}} functionality in conjunction with the record processing behavior. 



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