I also agree with this stance for an initial period of transition time, but
this obviously has a huge impact on contributions. Without any kind of end
date, I worry this is going to be policy indefinitely. Because of this, I
tend to agree with what Rob said in the previous email. Maybe once 2.0 is
Hi team,
Pierre is correct that I'm aiming to have a PR open today to expose the
flow analysis rules engine in the new UI. I'll be sure to address any
feedback left on my PR asap.
Best,
Shane
On Mon, Jun 17, 2024 at 12:03 PM Pierre Villard
wrote:
> Hi team,
>
> Happy to take care of the 1.26.1
Team,
As work continues with the new NiFi UI as well as the Jolt Transform UI, it
has come to my attention that these two interfaces utilize a library of
shared Angular components, directives, pipes, etc., located at
`nifi-frontend/src/main/frontend/libs/shared`. In my opinion, this shared
library
urrent versions of dependencies. I am currently in the process of
> migrating our content viewers into nifi-frontend following this model.
>
> Matt
>
> On Wed, Aug 21, 2024 at 10:59 AM Shane Ardell
> wrote:
>
> > Team,
> >
> > As work continues with the new NiFi
Hi Roy,
I have a bash script that may be of use to you. It rebuilds the UI and
copies it over to the target lib directory. It'll pick up .jsp changes as
well as JS and CSS. You can find it here:
https://gist.github.com/sardell/65d7c225a5c70056e3e7a54ec4027fdb
Best,
Shane
On Wed, Dec 22, 2021 at
+1 (non-binding).
Performed all verification steps listed in the helper guide and ran the
demo app.
Thanks for RMing, Scott!
On Wed, Jan 26, 2022 at 9:12 AM Matt Gilman wrote:
> +1 (binding) Release this package as nifi-fds-0.3.0
>
> Ran through release helper. Looks good. Thanks for RMing Sco
Hi Glenda,
Looking at the documentation, an approach you could take is to create an
AWSCredentialsProviderControllerService[1] as your AWS Credentials Provider
Service property value in the PutS3Object processor configuration
properties. You can assign a value to the access key and secret key
prop
I'm also working on https://issues.apache.org/jira/browse/NIFI-13765.
Although not critical, it would be nice to have this in the next release.
The fix is simple and I should have a PR open by tomorrow.
Best,
Shane
On Thu, Sep 19, 2024 at 7:23 AM Ferenc Kis wrote:
> Thank you for your feedback
+1 (non-binding)
On Thu, Nov 14, 2024 at 3:51 PM Kedvessy Péter wrote:
> +1 (non-binding)
>
> David Handermann ezt írta (időpont: 2024.
> nov. 13., Sze, 21:41):
>
> > Team,
> >
> > Following a discussion of future support for the NiFi version 1 series
> > [1], I am calling for a vote on the fol
+1 (non-binding)
Verified the release using the verification guide. Noticed the same thing
Peter did regarding the version on the Release Candidate Verification page
showing 2.3.0, but otherwise I was able to run through the verification
steps without issue. Designed and verified a basic flow. Ver
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
I am very much in support of everything Scott described in the previous
email in regard to the shared component library being the successor to the
legacy NiFi FDS library. I am really enjoying the NX monorepo architecture
and shared library the new UIs use, and it is something I'm leveraging in
my
12 matches
Mail list logo
