[
https://issues.apache.org/jira/browse/NIFI-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983195#comment-14983195
]
Joe Skora commented on NIFI-812:
--------------------------------
Ok, I partially misunderstood this one originally. "Read twice, code once."
*Will an "Add Response As Request Attribute" property satisfy this
requirement?*
Defaulting to "No", it wouldn't bloat the attribute set unless used. And,
there's no need to add it to the Response flow file as RouteOnContent will
already work in that case.
> InvokeHTTP should optionally store response body as a flowfile attribute
> ------------------------------------------------------------------------
>
> Key: NIFI-812
> URL: https://issues.apache.org/jira/browse/NIFI-812
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Joseph Witt
> Priority: Minor
>
> On a thread from Aug 3 on dev@nifi titled 'Route Original Flow File Base on
> InvokeHTTP Response' it was suggested that it could be useful to capture the
> response body as a flow file attribute. This would allow for
> RouteOnAttribute, for example, to be used to route the flowfile based on
> content within that response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
