James, I share your viewpoint here. Our RPM support to date was superficial and I think recent efforts reflect community driven interest in seeing it improve. I just commented on the ticket that I plan to merge it as-is. Will wait a bit to see if there are any other viewpoints on it. But I'd really like to include it with the 0.5.0 release.
As for status of the release otherwise: - Matt put in the patch last night for limiting the amount of viewable state coming back to the client side for the new state management. I plan to merge that soon. Looks good. - Aldrin is currently working on improving the implementation of ListFile to not require so much state to be held which was the root concern anyway. At this time there is no plan to block users of the state management feature from holding 'too much' state. That is something we'll need to document and advise just like flow file attributes today. Tony is poised to go after the RC tasks to create an RC. If we can knock out those two items + the RPM effort this release is pretty exciting. Thanks Joe On Tue, Feb 9, 2016 at 12:02 PM, James Wing <[email protected]> wrote: > I think it's actually a great time to include NIFI 1461 to improve the RPM > with a non-root user and group. With respect to backward compatibility, > 0.5.0 will also include a fix for NIFI-1454, and I'm skeptical that anyone > was successfully using the RPM output from the Maven build before that > fix. As part of NIFI-1454, we have changed the name of the RPM from > "nifi-assembly" to just "nifi", which I believe would break any upgrade > chain. > > Suggested text for the migration notes: > > The RPM distribution has been significantly improved. The name of the RPM > is now "nifi". The NiFi RPM installation will now create a "nifi" user and > group to own the installed files, while retaining and reusing existing > "nifi" users and groups. RPM users should install the RPM as a new package > install, rather than an upgrade, and port their configuration and > repository data to the new installation. > > On Mon, Feb 8, 2016 at 8:24 PM, Tony Kurc <[email protected]> wrote: > >> Joe, >> We'd need some migration notes changes added 1461. However, it does change >> the way the rpm works by a little bit. If people are integrating/deploying >> with rpms, it might be a breaking change. >> >> Tony >> >> On Mon, Feb 8, 2016 at 11:12 PM, Joe Witt <[email protected]> wrote: >> >> > Tony, >> > >> > It was what appears to have become NIFI-1492 that I personally felt >> > was important to get with state management because it will limit the >> > amount of state we return back to the client/UI. I am concerned about >> > the amount of state ListFile can generate in some cases and I think >> > that needs to be solved but it doesn't need to hold up the release. >> > >> > Also, what do you think about including 1461? It was requested by >> > Andre, implemented by Puspendu, validated by James Wing. I've not had >> > a chance to go through it yet but that it has such solid community >> > effort behind it is a huge plus. Will take a look at that first thing >> > tomorrow and provide feedback. >> > >> > Thanks >> > Joe >> > >> > >> > >> > >> > >> > >> > >> > On Mon, Feb 8, 2016 at 8:32 PM, Tony Kurc <[email protected]> wrote: >> > > I've gotten a couple out of band "hold off on the RCs", so I won't be >> > > cutting RC2 tonight. >> > > >> > > On Mon, Feb 8, 2016 at 2:27 PM, Tony Kurc <[email protected]> wrote: >> > > >> > >> All, >> > >> I'm hoping many of you are trying out the RC1 for functionality and >> > >> ideally haven't found any issues beyond those already patched. I was >> > >> planning on pulling together an RC2 tonight, so please, if you have >> > found >> > >> some other critical issues, please bring it up on this dev list. >> > >> >> > >> Tony >> > >> >> > >>
