There are only a couple issues remaining from NIFIDEVS-12400 <https://issues.apache.org/jira/browse/NIFI-12400>. Although, this issue is marked as resolved. I don't want the following unresolved issues to fall through the cracks prior to the final 2.0.0 release:
https://issues.apache.org/jira/browse/NIFI-13318 https://issues.apache.org/jira/browse/NIFI-13319 These add the 'Stop & Configure' and 'Disable & Configure' options to the UI of processors and controller services. This is an extremely useful feature used frequently. Thanks, Mark On Sun, Aug 11, 2024 at 7:04 AM Jens M. Kofoed <jmkofoed....@gmail.com> wrote: > With access policies, I mean the possibility to only allow certain "users" > to see and access specifics input/output ports. So while system A can share > many S2S ports, system B can only see/access ports for system B and system > C can only see/access ports for system C. I know I can do something similar > with InvokeHTTP, inputs ports. But each processor will have to bind to its > own port, right? > Kind Regards > Jens M. Kofoed > > Den søn. 11. aug. 2024 kl. 12.54 skrev Jens M. Kofoed < > jmkofoed....@gmail.com>: > > > Dear Joe > > > > I'm not quite sure how to understand your comment about S2S. Will > > Site-To-Site communication as it is today going to be removed from NiFi > in > > the future? > > I'm aware of many places where S2S is in use. The benefit of only having > 2 > > ports open in your firewall (https+S2S), and combining it with access > > policies which is able to connect to specifics input/output ports is very > > useful. If S2S is going to be removed, what will be the replacement? > > > > Kind regards > > Jens M. Kofoed > > > > Den fre. 9. aug. 2024 kl. 16.58 skrev Joe Witt <joe.w...@gmail.com>: > > > >> It is incredibly tempting to keep removing crusty bits like the XML and > >> S2S > >> as we are genuinely so much better off now having made so much tech debt > >> progress. Huge thanks to you in particular, David! But I do agree with > >> your view. > >> > >> I think right on the heels of the last vestige of old UI/content viewing > >> we > >> push for the official 2.0 release. > >> > >> I'd actually think we consider a 3.0 to be one year later which dumps > >> complex config models and S2S (at least the client impl) and continues > >> cleanup but otherwise incurs no user/migration impact. But that is a > >> fairly off the cuff mention. > >> > >> Thanks > >> > >> On Fri, Aug 9, 2024 at 7:21 AM David Handermann < > >> exceptionfact...@apache.org> > >> wrote: > >> > >> > Arpad, > >> > > >> > Thanks for initiating the discussion! I think we are getting very > >> > close to ready for a GA release of NiFi 2.0. > >> > > >> > The last major element I am aware of right now is some reworking of > >> > content viewer integration. Jira issue NIFI-13632 [1] highlights some > >> > general issues to be addressed, bringing the content viewer > >> > integration in line with the rest of the redesigned web user > >> > interface. I will defer to Matt Gilman and others for details. I'm > >> > not aware of anything else in particular, but this particular area is > >> > important as it relates to the contract between the main application > >> > and content viewers. > >> > > >> > Beyond that, there are other framework issues I would like to address > >> > in the future, such as the configuration structure that requires > >> > multiple XML files, and the Site-to-Site client library. However, in > >> > the interest of keeping changes scoped, I believe those can be > >> > addressed down the road. > >> > > >> > With that background, as soon as we are in a good position with the > >> > content viewer integration, we should proceed to preparing for a > >> > release. > >> > > >> > Regards, > >> > David Handermann > >> > > >> > [1] https://issues.apache.org/jira/browse/NIFI-13632 > >> > > >> > On Thu, Aug 8, 2024 at 5:57 PM Arpad Boda <ab...@apache.org> wrote: > >> > > > >> > > Team, > >> > > > >> > > Tremendous amount of effort has been put into NiFi 2.0 so far and I > >> > haven't > >> > > seen breaking changes introduced during the last few weeks, so I > >> wonder > >> > > where you think we are in the process of making it final(GA)? > >> > > Do you see features missing, things that need to be either updated > or > >> > > deprecated, breaking api changes introduced? > >> > > > >> > > Don't get me wrong, I have no intent to push the community to > release > >> 2.0 > >> > > as soon as we can, the goal of this thread is to have a common > >> > > understanding of where we are in the process and what we need to > >> achieve > >> > to > >> > > get there. > >> > > > >> > > Thanks in advance for sharing your thoughts, opinions! > >> > > > >> > > Cheers, > >> > > Arpad > >> > > >> > > >
