[jira] [Comment Edited] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable

["David Handermann (Jira)" <ji...@apache.org>]

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

David Handermann edited comment on NIFI-9894 at 12/9/22 7:43 PM:
-----------------------------------------------------------------

No new activity right now.

This is an issue where it would be helpful to get some additional input.

[~markap14] or [~pvillard] do either of you have additional comments on this feature? It could be introduced through a new strategy property, although InvokeHTTP already has a large number of properties. As indicated by the duplicated issues, however, this has come up a number of times.


was (Author: exceptionfactory):
No new activity right now.

This is an issue where it would be helpful to get some additional input.

[~markap14] or [~pvillard]] do either of you have additional comments on this feature? It could be introduced through a new strategy property, although InvokeHTTP already has a large number of properties. As indicated by the duplicated issues, however, this has come up a number of times.

> Enhance InvokeHTTP process - Send content through body variable
> ---------------------------------------------------------------
>
>                 Key: NIFI-9894
>                 URL: https://issues.apache.org/jira/browse/NIFI-9894
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.15.3
>            Reporter: Denis Jakupovic
>            Priority: Trivial
>
> Hey,
> could you please implement an attribute in the InvokeHTTP processor where the processor sends a "body attribute" as raw content instead of the current content triggering an InvokeHTTP processor.
> The process of sending JSON files through the processor currently is:
> 1. ReplaceText with content if needed
> 2. Call Invoke HTTP
> 3. Read Reponse variable or the new content created
> 3. ReplaceText with enriched content 
> Yes I know in Nifi 1.16 there is are two new processor for enrichment which needs then to be merged again. However, by working with a lot of RESTful services its quite a pain always to replace the content. The data lineage and provenance increases a lot as well.
> imho better process in some use case:
>  # InvokeHTTP with attibute as body
>  # Read the "original" route instead of the response and read response adde attribute. (feature already available)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)