and collect stats about those processors.
-Karthik
From: Daniel Chaffelson [mailto:chaffel...@gmail.com]
Sent: Wednesday, August 15, 2018 12:40 AM
To: users@nifi.apache.org
Subject: Re: [EXT] Re: Get all Processors
Hi Karthik,
I have already implemented this in NiPyApi, assuming a Python automation
...@gmail.com]
> Sent: Tuesday, August 14, 2018 9:17 AM
> To: users@nifi.apache.org
> Subject: Re: [EXT] Re: Get all Processors
>
> You could probably achieve the same thing but traversing the process
> groups and asking each one for its processors without the
> include
, 2018 9:17 AM
To: users@nifi.apache.org
Subject: Re: [EXT] Re: Get all Processors
You could probably achieve the same thing but traversing the process groups and
asking each one for its processors without the includeDescendantGroups=true.
It would be more complex on the client side, but would avoid
lto:pierre.villard...@gmail.com]
> Sent: Tuesday, August 14, 2018 2:20 AM
> To: users@nifi.apache.org
> Subject: Re: [EXT] Re: Get all Processors
>
>
>
> Hi Karthik,
>
>
>
> Are you running a cluster or standalone NiFi? What's your default read
> timeout value in
: Re: [EXT] Re: Get all Processors
Hi Karthik,
Are you running a cluster or standalone NiFi? What's your default read timeout
value in nifi.properties? I believe the default value is a bit low when you
start reaching thousands of processors.
nifi.cluster.node.read.timeout=5 sec
Pierre
2018-08
to get all processors and
> the controller Services they refer (if any?). Not sure how to get the
> information I need in one call.
>
> -Karthik
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Monday, August 13, 2018 2:07 PM
> To: users@nifi.ap
the information I
need in one call.
-Karthik
-Original Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Monday, August 13, 2018 2:07 PM
To: users@nifi.apache.org
Subject: [EXT] Re: Get all Processors
Karthik
I believe that call is/was very expensive on the server side. You might
