All,
I would like to call a vote for NIP-1 [1] to add a VerifiableRegistryClient
interface to verify Registry Client implementations. I can't find the
DISCUSS thread in the archive but there was a reply from Bryan Bende on Oct
8, 2024, quoted here:
"It seems like a reasonable change to me and wou
Hey Michael,
You should be good to go.
Thanks
-Mark
> On May 7, 2025, at 2:12 PM, Michael Reiche
> wrote:
>
>
>
> Hello -
>
> I would like contributor status work on
> https://issues.apache.org/jira/browse/NIFI-10752. My jira name is mikereiche
> .
>
> Michael Reiche
>
>
>
Hello -
I would like contributor status work on
https://issues.apache.org/jira/browse/NIFI-10752. My jira name is mikereiche .
Michael Reiche
Hi Dev Community, Can you please throw some light please?
On Sun, May 4, 2025, 11:26 PM Subrahmanya Oruganti <
chakravarthi.oruga...@gmail.com> wrote:
> Dear DEV Community,
>
> The nifi-api/flow/metrics/prometheus api endpoint is generating prometheus
> metrics from componentEventRepository field
Hi NIFI Team,
I am reaching out to you for the information regarding NIFI heap usage.
Please find the below details about NIFI and system setup we are using.
NIFI version: 1.27.0
Environment details: 14 NIFI nodes cluster, running in Kubernetes where each
pod allocated with 30 GB disk.
use case:
Hi Bharath,
I'd recommend not using the embedded ZooKeeper server if you want better
control over the version you wish to use. NiFi 1.x is effectively end of
life so you are unlikely to see updates to the bundled ZooKeeper version.
Standing up a separate ZooKeeper cluster or upgrading to NiFi 2.x w
