You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by ski n <ra...@gmail.com> on 2019/08/02 14:14:33 UTC
Re: [EXT] Re: NiFi 2.0 Roadmap
"a Flow Registry that can hold extensions and we can then make nifi 2.0
fundamentally about distributing nifi as a kernel (small as possible) and
all extensions come from a flow registry on demand. "
Nice! Great to hear NiFi as an extensible platform. I would see that the
NiFi Registry is linked to a repository. Where one is the official
repository and another for community. At this repo/library people can
public put Processors/Services/Templates/Extensions. Browsing/Installing
should be similar to an app store (Jenkins does this nicely and also
Node-Red Library https://flows.nodered.org).
Another thing that I would like to see is that for developing/testing you
don't need to leave NiFi. For example directly code/debug
(codemirror/ace/monaco) and unit test it with input/output of a flowfile
for a specific processor.
Also a thing is making the GUI more responsive (rendering) and comfortable
(like undo). Most big features are already on Confluence:
https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals
Raymond
Op vr 14 jun. 2019 om 22:59 schreef Peter Wicks (pwicks) <pwicks@micron.com
>:
> I've also heard something about a big change to the way relationships
> work. Maybe grouping relationships into larger groupings "failure" as a
> parent, with multiple optional/fine grained, children. Something like
> that. If that rings a bell, maybe add it to your list 😊.
>
> -----Original Message-----
> From: Joe Witt <jo...@gmail.com>
> Sent: Friday, June 14, 2019 11:31 AM
> To: dev@nifi.apache.org
> Subject: [EXT] Re: NiFi 2.0 Roadmap
>
> It makes sense there would be an mvp set of registry capability and thus a
> dependency for nifi 2.0 on registry readiness/version. Otherwise I would
> largely hope not.
>
>
> On Fri, Jun 14, 2019 at 1:29 PM Otto Fowler <ot...@gmail.com>
> wrote:
>
> > Will that effort or planning be across all the nifi projects? minifi
> > / cpp / registry etc?
> >
> >
> > On June 14, 2019 at 13:01:36, Joe Witt (joe.witt@gmail.com) wrote:
> >
> > Peter,
> >
> > Yeah I think we're all circling around similar thoughts on things
> > which are 'best for a major release' and we need to start codifying
> > that. At the same time we need this to be focused on items which can
> > only reasonably happen in a major release and not become a new kitchen
> > sink for JIRAs/ideas. We should frame up a wiki page for this effort.
> > I'm happy to kick that off soon (time permitting). In my mind the key
> > domino here is having a Flow Registry that can hold extensions and we
> > can then make nifi
> > 2.0 fundamentally about distributing nifi as a kernel (small as
> > possible) and all extensions come from a flow registry on demand.
> > Other obvious things like Java 11 as the base requirement and killing
> > off deprecated things come to mind.
> >
> > Thanks
> >
> > On Fri, Jun 14, 2019 at 11:45 AM Peter Wicks (pwicks)
> > <pw...@micron.com>
> > wrote:
> >
> > > I've seen a lot of comments along the line of, "I don't think this
> > > will happen before NiFi 2.0". Do we have a roadmap/list somewhere of
> > > the big general changes planned for NiFi 2.0 or some kind of 2.0
> roadmap?
> > >
> > > --Peter
> > >
> >
>
Re: [EXT] Re: NiFi 2.0 Roadmap
Posted by Joe Witt <jo...@gmail.com>.
Ryan
No specific developments for a 2.0 push right now. There is still so
much progress being made without breaking any major eggs that we've just
kept moving ahead. However, it is likely that once we have a clear path to
split out nars from the core framework that we should really dive into
this. We have no choice but to not grow our convenience binary at this
point.
Thanks
On Tue, Feb 23, 2021 at 2:53 PM Ryan Hendrickson <
ryan.andrew.hendrickson@gmail.com> wrote:
> Resurrecting an old thread here... Any updates on a 2.0 or new major
> release of NiFi?
>
> Thanks,
> Ryan
>
> On Fri, Aug 2, 2019 at 10:14 AM ski n <ra...@gmail.com> wrote:
>
> > "a Flow Registry that can hold extensions and we can then make nifi 2.0
> > fundamentally about distributing nifi as a kernel (small as possible) and
> > all extensions come from a flow registry on demand. "
> >
> > Nice! Great to hear NiFi as an extensible platform. I would see that the
> > NiFi Registry is linked to a repository. Where one is the official
> > repository and another for community. At this repo/library people can
> > public put Processors/Services/Templates/Extensions. Browsing/Installing
> > should be similar to an app store (Jenkins does this nicely and also
> > Node-Red Library https://flows.nodered.org).
> >
> > Another thing that I would like to see is that for developing/testing you
> > don't need to leave NiFi. For example directly code/debug
> > (codemirror/ace/monaco) and unit test it with input/output of a flowfile
> > for a specific processor.
> >
> > Also a thing is making the GUI more responsive (rendering) and
> comfortable
> > (like undo). Most big features are already on Confluence:
> > https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals
> >
> >
> > Raymond
> >
> >
> >
> >
> > Op vr 14 jun. 2019 om 22:59 schreef Peter Wicks (pwicks) <
> > pwicks@micron.com
> > >:
> >
> > > I've also heard something about a big change to the way relationships
> > > work. Maybe grouping relationships into larger groupings "failure" as a
> > > parent, with multiple optional/fine grained, children. Something like
> > > that. If that rings a bell, maybe add it to your list 😊.
> > >
> > > -----Original Message-----
> > > From: Joe Witt <jo...@gmail.com>
> > > Sent: Friday, June 14, 2019 11:31 AM
> > > To: dev@nifi.apache.org
> > > Subject: [EXT] Re: NiFi 2.0 Roadmap
> > >
> > > It makes sense there would be an mvp set of registry capability and
> thus
> > a
> > > dependency for nifi 2.0 on registry readiness/version. Otherwise I
> would
> > > largely hope not.
> > >
> > >
> > > On Fri, Jun 14, 2019 at 1:29 PM Otto Fowler <ot...@gmail.com>
> > > wrote:
> > >
> > > > Will that effort or planning be across all the nifi projects? minifi
> > > > / cpp / registry etc?
> > > >
> > > >
> > > > On June 14, 2019 at 13:01:36, Joe Witt (joe.witt@gmail.com) wrote:
> > > >
> > > > Peter,
> > > >
> > > > Yeah I think we're all circling around similar thoughts on things
> > > > which are 'best for a major release' and we need to start codifying
> > > > that. At the same time we need this to be focused on items which can
> > > > only reasonably happen in a major release and not become a new
> kitchen
> > > > sink for JIRAs/ideas. We should frame up a wiki page for this effort.
> > > > I'm happy to kick that off soon (time permitting). In my mind the key
> > > > domino here is having a Flow Registry that can hold extensions and we
> > > > can then make nifi
> > > > 2.0 fundamentally about distributing nifi as a kernel (small as
> > > > possible) and all extensions come from a flow registry on demand.
> > > > Other obvious things like Java 11 as the base requirement and killing
> > > > off deprecated things come to mind.
> > > >
> > > > Thanks
> > > >
> > > > On Fri, Jun 14, 2019 at 11:45 AM Peter Wicks (pwicks)
> > > > <pw...@micron.com>
> > > > wrote:
> > > >
> > > > > I've seen a lot of comments along the line of, "I don't think this
> > > > > will happen before NiFi 2.0". Do we have a roadmap/list somewhere
> of
> > > > > the big general changes planned for NiFi 2.0 or some kind of 2.0
> > > roadmap?
> > > > >
> > > > > --Peter
> > > > >
> > > >
> > >
> >
>
Re: [EXT] Re: NiFi 2.0 Roadmap
Posted by Ryan Hendrickson <ry...@gmail.com>.
Resurrecting an old thread here... Any updates on a 2.0 or new major
release of NiFi?
Thanks,
Ryan
On Fri, Aug 2, 2019 at 10:14 AM ski n <ra...@gmail.com> wrote:
> "a Flow Registry that can hold extensions and we can then make nifi 2.0
> fundamentally about distributing nifi as a kernel (small as possible) and
> all extensions come from a flow registry on demand. "
>
> Nice! Great to hear NiFi as an extensible platform. I would see that the
> NiFi Registry is linked to a repository. Where one is the official
> repository and another for community. At this repo/library people can
> public put Processors/Services/Templates/Extensions. Browsing/Installing
> should be similar to an app store (Jenkins does this nicely and also
> Node-Red Library https://flows.nodered.org).
>
> Another thing that I would like to see is that for developing/testing you
> don't need to leave NiFi. For example directly code/debug
> (codemirror/ace/monaco) and unit test it with input/output of a flowfile
> for a specific processor.
>
> Also a thing is making the GUI more responsive (rendering) and comfortable
> (like undo). Most big features are already on Confluence:
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals
>
>
> Raymond
>
>
>
>
> Op vr 14 jun. 2019 om 22:59 schreef Peter Wicks (pwicks) <
> pwicks@micron.com
> >:
>
> > I've also heard something about a big change to the way relationships
> > work. Maybe grouping relationships into larger groupings "failure" as a
> > parent, with multiple optional/fine grained, children. Something like
> > that. If that rings a bell, maybe add it to your list 😊.
> >
> > -----Original Message-----
> > From: Joe Witt <jo...@gmail.com>
> > Sent: Friday, June 14, 2019 11:31 AM
> > To: dev@nifi.apache.org
> > Subject: [EXT] Re: NiFi 2.0 Roadmap
> >
> > It makes sense there would be an mvp set of registry capability and thus
> a
> > dependency for nifi 2.0 on registry readiness/version. Otherwise I would
> > largely hope not.
> >
> >
> > On Fri, Jun 14, 2019 at 1:29 PM Otto Fowler <ot...@gmail.com>
> > wrote:
> >
> > > Will that effort or planning be across all the nifi projects? minifi
> > > / cpp / registry etc?
> > >
> > >
> > > On June 14, 2019 at 13:01:36, Joe Witt (joe.witt@gmail.com) wrote:
> > >
> > > Peter,
> > >
> > > Yeah I think we're all circling around similar thoughts on things
> > > which are 'best for a major release' and we need to start codifying
> > > that. At the same time we need this to be focused on items which can
> > > only reasonably happen in a major release and not become a new kitchen
> > > sink for JIRAs/ideas. We should frame up a wiki page for this effort.
> > > I'm happy to kick that off soon (time permitting). In my mind the key
> > > domino here is having a Flow Registry that can hold extensions and we
> > > can then make nifi
> > > 2.0 fundamentally about distributing nifi as a kernel (small as
> > > possible) and all extensions come from a flow registry on demand.
> > > Other obvious things like Java 11 as the base requirement and killing
> > > off deprecated things come to mind.
> > >
> > > Thanks
> > >
> > > On Fri, Jun 14, 2019 at 11:45 AM Peter Wicks (pwicks)
> > > <pw...@micron.com>
> > > wrote:
> > >
> > > > I've seen a lot of comments along the line of, "I don't think this
> > > > will happen before NiFi 2.0". Do we have a roadmap/list somewhere of
> > > > the big general changes planned for NiFi 2.0 or some kind of 2.0
> > roadmap?
> > > >
> > > > --Peter
> > > >
> > >
> >
>