[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655586#comment-17655586 ]
Mark Payne commented on NIFI-9894: ---------------------------------- [~exceptionfactory] I think it's a reasonable improvement to InvokeHTTP. We already have two properties "Put Response Body In Attribute" and "Request Body Enabled" that are true/false values. This is very unfortunate - it would have made much more sense to have these be values like "Response Body Destination" with values of {{{}FlowFile Content{}}}, {{{}Attribute{}}}, {{None}} and also allowing Request Body to be chosen as {{{}Expression Language{}}}, {{{}FlowFIle Content{}}}, or {{{}None{}}}. Perhaps as part of 2.0, we could consolidate these together. > 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)