Hello,
The slack mentioned in the 2.2.0 README is locked down to people that have an
apache.org email address, any chance I could get an invite?
Thank you
We're quite a ways back, but I do the development and I run on 1.28.1
(both NiFi and NiFi Registry). We have plans to move to 2.x someday.
It's hard to get customers to move forward.
On 3/4/25 10:22, Joe Witt wrote:
What versions Russ?
On Tue, Mar 4, 2025 at 10:15 AM Russell Bateman
wrote:
An alternative approach/future roadmap could be to consider integrating
non-Git storage variants of the NiFiFlowRegistryClient into NiFi itself,
e.g. the Filesystem, InMemory and Database variants from Registry itself.
That would allow users to take advantage of all of the good work that's
gone in
Based on Shane's efforts to modernise NiFi Registry UI I would prefer to
keep things as they are. I'm not aware of any concerns related to the
backend, so in case Shane and other members of the community contributing
to this effort can finish the works on the UI side I feel like there is
going to b
I am aware of environments where access to a Git server from the
operational host/cluster that's running NiFi and NiFi Registry would not be
available due to security or other constraints. Loss of a non-Git based
Flow version control option would impact such environments. That said, I
imagine such
Thank you for opening the discussion David.
We also make use of the NiFi registry both for Flow versioning and
automatic distribution of custom .nar artifacts to the clusters.
We thought about moving Flow versioning to a Git provider to both:
- profit from improved version history, and
- investig
Hi Kyle,
There’s no minimum amount to keep - it will always keep everything that it can
keep, up to the configured max. So in your case once you hit 10 GB of
provenance events it will age off the older events to make room for newer
events. And anything over 30 days will also be eliminated, for
We don't use a separate Git repository; only the simple solution the
NiFi Registry offers.
Maybe someday we'll go further, but, in the meantime, It's super useful
to us so we hope
never to see it disappear.
Thanks,
Russ Bateman
On 3/4/25 08:44, David Handermann wrote:
Team,
For more than two
What versions Russ?
On Tue, Mar 4, 2025 at 10:15 AM Russell Bateman
wrote:
> We don't use a separate Git repository; only the simple solution the
> NiFi Registry offers.
> Maybe someday we'll go further, but, in the meantime, It's super useful
> to us so we hope
> never to see it disappear.
>
>
Hello,
I created this Jira [1] toward the end of last year in hopes of migrating
NiFi Registry's UI similar to how we did for NiFi's UI. Aside from removing
these outdated dependencies from the UI, this work leverages the shared
component library that the new UIs share which results in a UX much c
Hi. Is there a “minimum provenance” to keep setting for a given processor?
Use-case is
1. User asks us to check provenance on one of their “weekly” workflows (for
data errors, etc.)
2. The “weekly” task’s provenance got deleted—perhaps from other, more
frequently executed processors, du
David,
First thanks for kicking off this thread.
I think the punchline of what you wrote is
"Current community work has focused on direct integration with Git-based
Flow Registry Clients, including GitHub, GitLab, and BitBucket. With the
Flow
Registry Client as an extension point itself, the NiFi
Team,
For more than two years, the NiFi Registry project has received
minimal maintenance attention. This is apparent from a review of
commits related to the nifi-registry directory [1], the majority of
which are incremental dependency version upgrades. As project
maintainers, we need to decide on
Hi
I need a couple of answers and have been unable to find them addressed
anywhere.
I have a working cluster of nifi 2.0.0m4 with tls, but I want to get oidc
working.
I finally figured to use admin identity to create a safe user to take over
with an ldap/oidc login, however despite having server an
14 matches
Mail list logo
