There really isn't a correct answer, it depends on how you are using
NiFi and how you want to organize your flows.
You can make a self-contained versioned process group that contains
all of the services with in it, and may or may not contain child
process groups.
You could also have services at t
The underlying issue is that there are components in your versioned
flow that can't be stopped for some reason.
Do you have any custom processors? If you try to stop everything
manually do all processors stop cleanly?
On Thu, Apr 11, 2019 at 7:22 AM saloni udani wrote:
>
> Ref: https://issues.ap
Hi Koji, that seems a pretty good idea, thanks for bringing it up! I wasn't
aware of nifi nano but definitely will give it a shot. =)
Thanks
Em qua, 10 de abr de 2019 às 22:38, Koji Kawamura
escreveu:
> Hi Eric,
>
> Although my knowledge on MiNiFi, Python and Go is limited, I wonder if
> "nanof
Ref: https://issues.apache.org/jira/browse/NIFI-5340
Any updates on this? We are facing same issue. For time being we have
increased connection and read timeout.
Thanks