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

David Handermann commented on NIFI-9894:
----------------------------------------

Thanks for the suggestions [~djakupovic].

With the understanding that there is some work involved to prepare the request 
body for InvokeHTTP, implementing support for reading the request body from an 
attribute creates greater potential for memory consumption issues related to 
storing content in attributes. Perhaps there is an alternative approach that 
would make it easier to prepare FlowFile content for the request body, as 
opposed to passing the content through an attribute.

Perhaps some additional details on the source of the JSON intended for sending 
through InvokeHTTP would help outline some possibilities.

> 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.1#820001)

Reply via email to