Thanks for initiating the discussion Joe!
I also would like to have the flow.xml removal work completed for a
milestone release since that is an integral part of the changes. Once that
is complete, there may be some other minor things, but I think getting that
done would be a good point to move
The Packager thing looks pretty close to being ready anyway. I dont see
that holding anything up on any line at this point.
I don't have any heartburn waiting for the flowxml and templates to get
tossed out as indeed that needs to happen regardless.
As far as M1 being a "the most disruptive"
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
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
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
