nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Taft <>
Subject Re: Route Original Flow File Base on InvokeHTTP Response
Date Tue, 04 Aug 2015 16:44:08 GMT
One option I think we kicked around at some point was to capture the
response body as a flowfile attribute in the original flowfile.  For
reasonably sized response bodies, this would work OK.  It would be a nice
way to handle your situation, because then the response becomes an
attribute of the request.

This would obviously take a code change, but adding a property to the
effect of "Capture response body as flowfile attribute" might be a nice

On Tue, Aug 4, 2015 at 11:57 AM, steveM <> wrote:

> My use case is I pull the doc id from the file, call a web service with
> that
> id. The service responds with json that I would then parse to determine
> where to route the document next. Sometimes the document might be new,
> sometimes an update is allowed, sometimes duplicates need to be put
> somewhere else.
> I was hoping I was missing something that allowed you to handle a response
> and just add an attribute to the original file (or something similar to
> handle this case).
> --
> View this message in context:
> Sent from the Apache NiFi (incubating) Developer List mailing list archive
> at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message