[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[
https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645470#comment-17645470 ] David Handermann commented on NIFI-9894: 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)
[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644266#comment-17644266 ] Denis Jakupovic commented on NIFI-9894: --- any news on this ? > 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)
[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519784#comment-17519784 ] David Handermann commented on NIFI-9894: Thanks for the reply [~djakupovic], that's a good point about storing the response in an attribute. Not ideal, but understandable given the nature of some use cases. > 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)
[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519669#comment-17519669 ] Denis Jakupovic commented on NIFI-9894: --- Hey [~exceptionfactory] , I can totally understand that it could lead to higher memory consumption. Other processors can take the content or an expression to trigger the processor as well (PutSQL for example). The InvokeHTTP processor lets you chose if you want to have the response in the content or an attribute (response as content is faster than response in attribute though, which is strange...) . Currently I have a use case where I enrich different data into attributes sequentially and write these attributes into json files e.g. Basically for the Invoke HTTP I always need to replace the content just to get a flag or some bytes of data from different REST sources. I could save at least the replacetext processor for these scenarios or a base64 decode processor as well, if I have a base64 value in an attribute stored before. Worst case: call N rest services # replace text # call invoke # replace text # call invoke # and so on The source can be anything, it depends on the rest service what it expects as an input. An expression language attribute for the invokehttp processor would be great. > 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)
[jira] [Commented] (NIFI-9894) Enhance InvokeHTTP process - Send content through body variable
[ https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
