NiFi 2.0 Roadmap

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

NiFi 2.0 Roadmap

Peter Wicks (pwicks)
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
Reply | Threaded
Open this post in threaded view
|

Re: NiFi 2.0 Roadmap

Joe Witt
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) <[hidden email]>
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
>
Reply | Threaded
Open this post in threaded view
|

Re: NiFi 2.0 Roadmap

Otto Fowler
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 ([hidden email]) 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) <[hidden email]>
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
>
Reply | Threaded
Open this post in threaded view
|

Re: NiFi 2.0 Roadmap

Joe Witt
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 <[hidden email]> 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 ([hidden email]) 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) <[hidden email]>
> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

RE: [EXT] Re: NiFi 2.0 Roadmap

Peter Wicks (pwicks)
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 <[hidden email]>
Sent: Friday, June 14, 2019 11:31 AM
To: [hidden email]
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 <[hidden email]> 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 ([hidden email]) 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)
> <[hidden email]>
> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [EXT] Re: NiFi 2.0 Roadmap

ski n
"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) <[hidden email]
>:

> 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 <[hidden email]>
> Sent: Friday, June 14, 2019 11:31 AM
> To: [hidden email]
> 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 <[hidden email]>
> 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 ([hidden email]) 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)
> > <[hidden email]>
> > 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
> > >
> >
>