nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <>
Subject Re: flowfile through invokehttp put
Date Thu, 16 May 2019 15:19:44 GMT
Well MergeContent in general is meant to take many flow files and
merge them together, so typically if you were using the flow file
format, the idea would be to create a single flow file where the
content contained (flow1 attrs, content)(flow 2 attrs, content) etc,
but what I was suggesting was to try to configure the processor in a
way that it never actually merges multiple flow files and just acts on
1 flow file. Essentially trying to use the packaging functionality of
MergeContent without the merging, since there is no corresponding
PackageContent processor to go with the UnpackContent processor.

On Thu, May 16, 2019 at 11:16 AM
<> wrote:
> Enviado desde mi HUAWEI P20 Pro
> Hi Michael,
> You might put all the relevant  attributes down mixed with the content in a special tag
> It is a kind of tricky because if there is Json structured data you will have to flatten
it first and then remove the special characters through ReplaceText, but you get the content
with the desired attributes included.
> Hope this tip helps.
> Regards,
> LC
> -------- Mensaje original --------
> Asunto: flowfile through invokehttp put
> De: Michael Di Domenico
> Para:
> CC:
> i'm pretty new to nifi, so i'm not sure this worded correctly or
> possible.  i have a flow which ends with an invokehttp process that
> does a PUT to web server.
> my naive understanding of this process is that when the flowfile hits
> invokehttp, the flow-attributes can be sent as key:value pairs via the
> http headers and the file-content gets PUT to the remote webserver via
> the http content-body
> is there a way to send the flow-attr and the flow-content (ie the
> entire flowfile) via the PUT?
> i have nifi on two ends of a connection, but in order to send the data
> from one to another i have to send it through a proxy like device.
> the near end of the device receives data from the PUT and far end does
> a POST to a remote nifi.
> this process works fine, but on the far end i only receive the file
> and none of the attributes (as expected).  i cannot configure the
> proxy device to pass key:value pairs in the http headers.  i'm
> presuming all the flow information would have to be sent via the PUT
> and then decoded by the nifi server on the far end.  i'm hoping
> there's a simple connector to do this rather then having me munge all
> the data together into something like an xml or json file and send
> that.

View raw message