How are your HandleHttpResponse timeouts set?
On Thu, 11 Jul 2019, at 16:02, Carlos Manuel Fernandes (DSI) wrote:
> Hello, I think i discover the problem with content not claimed, its wired,
> the problem only happens in nifi web services handleHttpRequest-> .. ->
> HandleHttpResponse.
>
>
That’s a cool workaround!! Thanks for sharing.
On Thu, 11 Jul 2019, at 16:57, James McMahon wrote:
> Update: we have another solution path that seems to give a very useful
> workaround for this challenge pre-1.8. If depends on having a messaging queue
> that can be read by ConsumeAMQP.
> Use
I have the same behaviour, with the same setup (container, “external” mount to
network drive) on 1.9.2
On Thu, 11 Jul 2019, at 21:08, Mikhail Rolshud (BLOOMBERG/ 120 PARK) wrote:
> This is a clean install of 1.9.2
> And I can see the provenance events for a couple of days if I wipe out
>
Build a simpe data flow using nifi, create template as xml, transform the xml
to config.yml using minifi-toolkit-0.5.0/bin/config.sh
But there's error after start minifi
ERROR [main] o.apache.nifi.controller.FlowController Could not create
Processor of type org.apache.nifi.cdc.mys
This is a clean install of 1.9.2
And I can see the provenance events for a couple of days if I wipe out
provenance_repository and restart the node.
After awhile nifi seems to keep writing them but not showing anything in ui.
From: users@nifi.apache.org At: 07/11/19 15:01:21To: Mikhail Rolshud
Hello
I suspect you have to add the new policy. Please see in the migration
guide from old version you had until now.
Thanks
On Thu, Jul 11, 2019, 2:56 PM Mikhail Rolshud (BLOOMBERG/ 120 PARK) <
mrols...@bloomberg.net> wrote:
> Hi,
>
> We noticed that after some time 1.9.2 stops showing
Hi Joe,
The message is shown based on this logic:
if (ui.value > 0 && (processor.inputRequirement === 'INPUT_FORBIDDEN'
|| processor.inputRequirement === 'INPUT_ALLOWED'))
The reasoning is because run duration > 0 means calls to the session
are being batched, so a source processor may read data
Hi, I'm curious about the Run Duration warning:
"Source Processors with a run duration greater than 0ms and no incoming
connections could lose data when NiFi is shutdown."
I notice not all processors have this warning when you set their run
duration larger than 0ms. Is there a specific
I am troubleshooting an Execute script processor that takes a JSON response
from a web API and converts it to an HTML table. When I run the code on my
local Windows 10 machine, the processor errors out with an encoding error
very similar to the one mentioned in this Hortonworks forum post
Update: we have another solution path that seems to give a very useful
workaround for this challenge pre-1.8. If depends on having a messaging
queue that can be read by ConsumeAMQP.
Use ListFile to establish your set of zero-byte flowfiles -- essentially,
metadata about the files you want to read
Hello, I think i discover the problem with content not claimed, its wired, the
problem only happens in nifi web services handleHttpRequest-> .. ->
HandleHttpResponse.
For example, in this flow : GenerateFlowFile->FetchFile->PutFile after two
minutes the content is claimed.
But if call
11 matches
Mail list logo
