nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <joe.w...@gmail.com>
Subject Re: Route Original Flow File Base on InvokeHTTP Response
Date Wed, 05 Aug 2015 02:16:25 GMT
https://issues.apache.org/jira/browse/NIFI-812

On Tue, Aug 4, 2015 at 12:52 PM, Joe Witt <joe.witt@gmail.com> wrote:
> Again with adam.  Will make a jira and knock that out.  Will also pursue
> what bryan mentioned though that will take longer
>
> On Aug 4, 2015 12:44 PM, "Adam Taft" <adam@adamtaft.com> wrote:
>>
>> 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
>> feature.
>>
>>
>> On Tue, Aug 4, 2015 at 11:57 AM, steveM <stephen.c.metcalf@lmco.com>
>> 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:
>> >
>> > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Route-Original-Flow-File-Base-on-InvokeHTTP-Response-tp2317p2343.html
>> > Sent from the Apache NiFi (incubating) Developer List mailing list
>> > archive
>> > at Nabble.com.
>> >

Mime
View raw message