nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Ghigiarelli <briang...@gmail.com>
Subject Re: Connecting NiFi Processors without Drawing Lines
Date Tue, 14 Jul 2015 01:58:55 GMT
Yeah, I think that would do the trick!

On Mon, Jul 13, 2015 at 7:21 PM, Joe Witt <joe.witt@gmail.com> wrote:

> Brian
>
> So adding a template to the flow is a single call and connecting its output
> is a second call.  Are you simply looking for a single call that would do
> both?
>
> Just want to make sure i follow the idea.
>
> One thing that might make sense is to allow a user to drag a template onto
> a target component which we would treat as signifying that this is where
> the output of that group goes.  This would be cool so long as there is a
> single output port of the template being instantiated.
>
> Am i in the ballpark?
> On Jul 13, 2015 7:08 PM, "Brian Ghigiarelli" <brianghig@gmail.com> wrote:
>
> > Hi all,
> >
> > Is there a way in NiFi to connect two processors without manually drawing
> > the line between them (or calling the REST interface to create that
> > connection) ?
> >
> > To better describe this particular use case, we have Template A as our
> main
> > flow.  We can deploy Template A onto our main Instance A, and everything
> > looks great.
> >
> > Instance B uses the same template, but has an additional ingress path, so
> > we have created a smaller Template B to pull in that data. We'd like
> > Template B to drop-in to NiFi and automatically output to one of the
> > processors in Template A without having to manually connect them each
> time
> > in order to ease the burden of the deployment.
> >
> > From a flow layout, it looks like:
> >
> > *Instance A:*
> > Ingress A --> Normalize --> Magic
> >
> > *Instance B:*
> > Ingress A --|
> >                    --> Normalize --> Magic
> > Ingress B --|
> >
> > Any suggestions would be greatly appreciated. Thanks!
> >
> > --
> > Brian Ghigiarelli
> >
>



-- 
Brian Ghigiarelli
570-878-9139

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message