Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 (non-binding) Cheers, Chris Sampson On Sat, 17 Jul 2021, 03:06 Andrew Lim, wrote: > +1 > > > On Jul 16, 2021, at 2:19 PM, Matt Burgess wrote: > > > > All, > > > > We've been asked to record our consensus for the move of NiFi Registry > > to the NiFi codebase in a mailing list thread for

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 > On Jul 16, 2021, at 2:19 PM, Matt Burgess wrote: > > All, > > We've been asked to record our consensus for the move of NiFi Registry > to the NiFi codebase in a mailing list thread for posterity. Most > discussion happened on the PR but INFRA would like a link to this > thread showing

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 (non-binding) On Fri, Jul 16, 2021 at 4:44 PM Otto Fowler wrote: > +1 (non-binding) > > From: Matt Burgess > Reply: dev@nifi.apache.org > Date: July 16, 2021 at 14:20:20 > To: dev@nifi.apache.org > Subject: [DISCUSS] NiFi Registry -> NiFi consensus > > All, > > We've been asked to

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 (non-binding) From: Matt Burgess Reply: dev@nifi.apache.org Date: July 16, 2021 at 14:20:20 To: dev@nifi.apache.org Subject: [DISCUSS] NiFi Registry -> NiFi consensus All, We've been asked to record our consensus for the move of NiFi Registry to the NiFi codebase in a mailing list

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 (non-binding) I'm all in favor of NiFi Registry being part of the NiFi codebase. However, I'm discovering some build issues specific to nifi-registry when building on a private network. I consider this just growing pains, and fully support the overall concept and associated advantages! -Mark

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 -joey > On Jul 16, 2021, at 11:54 AM, Bryan Bende wrote: > > +1 > >> On Fri, Jul 16, 2021 at 2:31 PM Kevin Doran wrote: >> >> +1. >> On Jul 16, 2021, at 2:28 PM, Joe Witt wrote: >>> >>> Yep definitely. Thought this was sorted via the JIRA. >>> >>> +1 >>> >>> On Fri, Jul 16,

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 On Fri, Jul 16, 2021 at 2:31 PM Kevin Doran wrote: > > +1. > > > On Jul 16, 2021, at 2:28 PM, Joe Witt wrote: > > > > Yep definitely. Thought this was sorted via the JIRA. > > > > +1 > > > > On Fri, Jul 16, 2021 at 11:26 AM David Handermann > > wrote: > >> > >> Thanks for handling this,

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1. > On Jul 16, 2021, at 2:28 PM, Joe Witt wrote: > > Yep definitely. Thought this was sorted via the JIRA. > > +1 > > On Fri, Jul 16, 2021 at 11:26 AM David Handermann > wrote: >> >> Thanks for handling this, Matt. As one of the reviewers on the PR, I vote >> +1 (non-binding). >> >>

Re: [DISCUSS] NiFi Registry -> NiFi consensus

a HUGE +1 (binding) This is a great move forward to land many new features in NiFi. Le ven. 16 juil. 2021 à 20:26, David Handermann a écrit : > Thanks for handling this, Matt. As one of the reviewers on the PR, I vote > +1 (non-binding). > > Regards, > David Handermann > > On Fri, Jul 16,

Re: [DISCUSS] NiFi Registry -> NiFi consensus

Yep definitely. Thought this was sorted via the JIRA. +1 On Fri, Jul 16, 2021 at 11:26 AM David Handermann wrote: > > Thanks for handling this, Matt. As one of the reviewers on the PR, I vote > +1 (non-binding). > > Regards, > David Handermann > > On Fri, Jul 16, 2021 at 1:20 PM Matt Burgess

Re: [DISCUSS] NiFi Registry -> NiFi consensus

Thanks for handling this, Matt. As one of the reviewers on the PR, I vote +1 (non-binding). Regards, David Handermann On Fri, Jul 16, 2021 at 1:20 PM Matt Burgess wrote: > All, > > We've been asked to record our consensus for the move of NiFi Registry > to the NiFi codebase in a mailing list

[DISCUSS] NiFi Registry -> NiFi consensus

All, We've been asked to record our consensus for the move of NiFi Registry to the NiFi codebase in a mailing list thread for posterity. Most discussion happened on the PR but INFRA would like a link to this thread showing consensus from PMC members, committers, and the community. I didn't put

[ANNOUNCE] Apache NiFi 1.14.0 release

Hello The Apache NiFi team would like to announce the release of Apache NiFi 1.14.0. This is a significant feature, improvement, and stability focused release. With this release users will now find that a default out of the box NiFi starts with important security controls enabled by default!

Re: wget during build

Thanks for the feedback Matt. I created a JIRA ticket to track this. I also created a separate ticket to create root level profiles to exclude (or selectively choose) modules now part of nifi such as minifi, nifi-registry, etc. Any debate or opinions can be entered in the tickets

Re: wget during build

Mark, MiNiFi Java has been generating Windows artifacts for a while now (before it became part of NiFi), and there are quite a few users who deploy MiNiFi Java on Windows. In my experience, users deploying to small devices tend to prefer MiNiFi C++ as long as the target architecture is supported.

Re: NiFi Registry -> NiFi

This is the Way, Team :) Congrats on this effort! Andrew On Fri, Jul 16, 2021, 8:29 AM Matt Burgess wrote: > All, > > Now that [1] is merged, NiFi Registry is now officially in the NiFi > codebase! Thanks to all who participated in discussions, reviews, and > testing. Here are some notes on

Re: wget during build

Thanks for the explanation Kevin. And, I hope the transition to the JAR goes well. Meanwhile, I found another point in the build that is reaching out to an external location. The minifi assembly attempts to download some Windows executable (profile windows-service-assembly). This is active by

NiFi Registry -> NiFi

All, Now that [1] is merged, NiFi Registry is now officially in the NiFi codebase! Thanks to all who participated in discussions, reviews, and testing. Here are some notes on what this means going forward: - All future releases of NiFi Registry will be in lockstep with NiFi, as of the current

Re: wget during build

I just compared the contents of the swagger UI tarball from GitHub artifacts and the jar from maven central, and they definitely look like they both contain the same files we are rebuilding in NiFi Registry, so I have opened a ticket to migrate from using the download-maven-plugin pulling from

Re: wget during build

Good find! At a glance, I think this maven jar could work as a replacement. I’ll look into it. Regarding how we use the Swagger UI. When included, the NiFi Registry web server hosts the Swagger UI in addition to the Registry web app and REST API. I believe it is hosted at

Re: wget during build

Thanks for laying out some clear options Kevin. I haven't dug into the inner workings of this component, and don't yet understand why a tarball is necessary. I looked at your first option. While I didn't find a tarball, there does appear to be org.webjars.swagger-ui JAR component in common maven

Re: nifi 1.14.0

yes, bin/nifi.sh set-single-user-credentials On Fri, Jul 16, 2021 at 6:18 AM Chris Lim wrote: > Is there a way to change the username and password? > > Thanks, > Chris > > On Fri, Jul 16, 2021 at 13:35 Chris Sampson > wrote: > > > The username and password are printed to the logs during

Re: nifi 1.14.0

Hi Chris, Yes, you can use: ./bin/nifi.sh set-single-user-credentials Joe Virus-free. www.avast.com

Re: nifi 1.14.0

Is there a way to change the username and password? Thanks, Chris On Fri, Jul 16, 2021 at 13:35 Chris Sampson wrote: > The username and password are printed to the logs during startup, you can > obtain them there. > > > Cheers, > > Chris Sampson > > On Fri, 16 Jul 2021, 06:03 Roberto Vega, >