One caveat to my earlier comments - went through JIRAs and found this one hanging out. Ran into this while doing the NIFI-12988 refactor work.
https://issues.apache.org/jira/browse/NIFI-13080 We should not let the 'nifi-properties' module remain in the root lib nor the strange relationship to nifi-property-utils and we definitely do not want NiFiProperties to be referenced by anything outside the core framework. It isn't nearly as bad as it had been in the past as now we see only things which are framework extensions using it. But we do need to get that better handled and ensure nifi properties land as a jar within the framework nar and not in the extensions class path. That was the only thing I've found so far that really needs to be cleaned up prior to calling this done for 2x On Fri, Aug 9, 2024 at 9:39 AM Steven Matison <[email protected]> wrote: > This is awesome to hear. I recently moved all my personal stuff into 2.0 > space and everything working smoothly as expected. Now I can play with new > and forget old. > > > Amazing work from everyone who has helped the 2.x project get so far so > fast!! > > > > > On Fri, Aug 9, 2024 at 11:21 AM Douglas Reid <[email protected]> > wrote: > > > Thanks Joe. What’s a rough estimate to wrap up the final bits of work? > > > > > > > On Aug 9, 2024, at 10:58 AM, Joe Witt <[email protected]> wrote: > > > > > > 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 < > > [email protected]> > > > 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 <[email protected]> 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 > > >> > > > > >
