Ok, thanks!
From: Etienne Jouvin
Sent: Saturday, February 1, 2020 4:22 PM
To: users@nifi.apache.org
Subject: Re: InvokeHTTP & AttributesToJSON Help
Hi.
If I well understand, you can configure the InvokeHTTP to always output the
response.
In this
(still new).
>
>
>1. I want to route a status 500 to Failure. Not retry. The response
>contains a JSON message.
>2. Currently, I am routing the InvokeHTTP Retry with code 500 to
>AttributesToJSON to pull the response JSON from "invokehttp.response.body"
Hi,
I have probably 2 easy problems I can't seem to solve (still new).
1. I want to route a status 500 to Failure. Not retry. The response contains
a JSON message.
2. Currently, I am routing the InvokeHTTP Retry with code 500 to
AttributesToJSON to pull the response JSON from
, definitely the best thing that has happened to
> NiFi since bedtime stories [1].
> So my current flow is:
>
> GetFile (leave original file) ->
> ExtractHL7Attributes ->
> UpdateAttribute (for light conversions) ->
> AttributesToJSON (as flowfile-content) ->
> Jol
original file) ->
ExtractHL7Attributes ->
UpdateAttribute (for light conversions) ->
AttributesToJSON (as flowfile-content) ->
JoltTransformJSON (This could probably be replaced by record readers /
writers) ->
InvokeHTTP (call webservice) ->
FetchFile (using filename attribut
ed on the dataflow result.
> I have to work around NiFi to make the last step happen.
>
> I am setting the AttributesToJSON to replace the flowfile content because
> the Jolt transformer requires the JSON object to be in the flowfile content.
> There is no "original" relatio
result. I have to work around NiFi to make the last step happen.
I am setting the AttributesToJSON to replace the flowfile content because
the Jolt transformer requires the JSON object to be in the flowfile
content. There is no "original" relationship out of AttributesToJSON, so
this
flowfile attributes I wish to save to
> flowfile content as a JSON object. I employ processor AttributesToJSON.
>
> One of the attributes looks like so:
>
> options {"keyA":"valueA","keyB":"valueB"}
>
> The output from AttributesT
Hello. I have a simple set of three flowfile attributes I wish to save to
flowfile content as a JSON object. I employ processor AttributesToJSON.
One of the attributes looks like so:
options {"keyA":"valueA","keyB":"valueB"}
The output from Attribut
Bryan and Aldrin,
Thanks for your replies.
The user has already specified an order in the attributesToJSON processor’s
configuration. If we honor this order, we should be covered. Changing the
datatype to LinkedHashMap is exactly what I had in mind. I do not believe we
need to worry about
) <
pagibea...@micron.com> wrote:
> Hello all,
>
> I thought I would run this by you before I created a Jira ticket.
>
>
>
> The processor attributesToJSON does not create a JSON document with
> key/values in the same order as provided in the processor’s
ers@nifi.apache.org" <users@nifi.apache.org>
> Subject: Refer to original FlowFile after AttributesToJSON processor
>
> Is there a way to refer to original FlowFile after AttributesToJSON call?
> Destination set to flowfile-content.
> Or is there a way to produce a FlowF
apache.org<mailto:users@nifi.apache.org>"
<users@nifi.apache.org<mailto:users@nifi.apache.org>>
Subject: Refer to original FlowFile after AttributesToJSON processor
Is there a way to refer to original FlowFile after AttributesToJSON call?
Destination set to flowfile-con
Is there a way to refer to original FlowFile after AttributesToJSON call?
Destination set to flowfile-content.
Or is there a way to produce a FlowFile from an attribute?
I need to extract some properties from Twitter JSON, convert to a new JSON,
and after to extract another property from
card.url = http://mysite.com
But no matter how I try to use AttributesToJSON, I don't get the desired
result. I tried to pass "card" and "card.*" as arguments to Attributes List,
but they don't have the desired result.
And I don't like to repeat myself, but the documentation doesn't mention it
either...
Kind regards,
Jeroen
15 matches
Mail list logo
