[
https://issues.apache.org/jira/browse/NIFI-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
