I'm also hoping that both 1.x and 2.x lines can receive the PackageFlowFile processor that Mike Moser recently proposed. That way, the M1 release and the most recent 1.x release will have a simple (or logical) replacement for PostHTTP.
In general, it would be nice to have 1.x lined up with 2.0-M1 so that the transitional experience is as disruptive as it's going to be when 2.0-final is released. That is, I want all the things that can break to break, once a 2.0 milestone is released. From that perspective, I agree with Pierre that waiting for the flow.xml work to finalize makes the most sense, because then users can start getting a feel for how it will affect them. Lots of deployment scripts (think Ansible or equivalent) rely on the flow.xml.gz file specifically. The most disruptive parts of the 1.x to 2.x transition would ideally be realized as early as possible. Understand and agree with the urgency to get 2.0-M1 released, but also concerned that it doesn't allow a proper evaluation of all breaking changes just yet. /Adam On Tue, Sep 26, 2023 at 9:18 AM Pierre Villard <[email protected]> wrote: > Hey Joe, > > Definitely a +1 to get a M1 release ASAP. I'd still recommend waiting on > the flow.xml removal work to be merged. The reason being that users may > give useful feedback when they'll try NiFi 2.0 with existing flows coming > from NiFi 1.x and getting rid of all of the XML based stuff. There is also > a PR coming soon for the frontend work of the templates removal. Hopefully > both can be completed this week or next week. > > Pierre > > Le mar. 26 sept. 2023 à 17:35, Joe Witt <[email protected]> a écrit : > > > Team, > > > > The NiFi 2.0 release has more than 700 resolved JIRAs on it [1] and > growing > > every day. > > > > The NiFi 2.0 deprecation plan is well underway and largely complete [2]. > > > > We still need to remove a lot of now deprecated code, tests which are > never > > run and largely don't work, eliminate the flow.xml which has a JIRA/PR > > underway. And more. But we're getting close and we need to start > getting > > this in the hands of users. > > > > The docker image can now be built in 'nifi-docker/dockermaven' after a > full > > build from root with 'mvn install -Pdocker'. And it comes up with > Ubuntu, > > Java 21, Python 3.9, and NiFi 2.0 ready to roll with Python processors > > enabled. > > > > I propose we start closing down soon to make a NiFi 2.0 M1 release happen > > even before we have all the things done. We need to start getting > feedback > > and giving people a chance to work with it. > > > > Lastly, a huge thank you to the folks in the community that have been > > helping push towards 2.x with code changes, removals, reviews, bug > reports, > > etc.. Super awesome to see. NiFi 2.x is shaping up nicely to be useful > > not only for our well established user base which spans the globe and > every > > industry but now we are also seeing a lot of opportunity and fit for NiFi > > in these exciting AI use cases particularly involving orchestrating the > > data flows with embeddings, vector stores, and LLMs. And the Python > > capabilities in NiFi 2.x make NiFi far easier to use for the very > important > > data engineer user base. > > > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12339599 > > [2] > > > > > https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features > > > > Thanks > > Joe > > >
