On Thu, May 16, 2019 at 10:48 AM Bryan Bende wrote:
> The only other option I can think of is to use MergeContent with the
> Merge Format set to "FlowFile Stream v3" and configure the max and min
> entries to 1 so it doesn't really actually merge anything, but just
> writes out the new flow
On Thu, May 16, 2019 at 3:38 PM Andy LoPresto wrote:
>
> Bryan’s comments are definitely helpful around the additional work
> separation, but revisiting your initial question, did you try using Site To
> Site through the proxy? Koji Kawamura has done a lot of work on this [1][2]
> and I
Bryan’s comments are definitely helpful around the additional work separation,
but revisiting your initial question, did you try using Site To Site through
the proxy? Koji Kawamura has done a lot of work on this [1][2] and I believe
it’s pretty successful. There are example configurations and
On Thu, May 16, 2019 at 11:20 AM Bryan Bende wrote:
>
> 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,
ere 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 ---
Enviado desde mi HUAWEI P20 ProHi Michael,You might put all the relevant attributes down mixed with the content in a special tag (Jolt) 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
On Thu, May 16, 2019 at 10:48 AM Bryan Bende wrote:
>
> Normally this would all be handled for you with site-to-site, but not
> sure that can be made to work with your custom proxy. Before
> site-to-site there was PostHttp and ListenHttp, and PostHttp has an
> options for "Send As Flow File".
Normally this would all be handled for you with site-to-site, but not
sure that can be made to work with your custom proxy. Before
site-to-site there was PostHttp and ListenHttp, and PostHttp has an
options for "Send As Flow File". PostHTTP is marked as deprecated
because generally you should use
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
