Broadcasting Flow File

[Pierre Villard <pi...@gmail.com>]

Hi,

I have a use case where I need to "broadcast" a flow file to multiple
processors. At the moment, the only way I see to do that is to combine a
DuplicateFlowFile processor with a DistributeLoad processor. It seems to
work fine, but I am wondering if it would be more user friendly to have a
dedicated processor for this kind of operation? If you think so, I'll be
happy to have it done.

Pierre

Re: Broadcasting Flow File

[Pierre Villard <pi...@gmail.com>]

Yes that's correct. I didn't notice the possibility to use the same
relationship multiple times.
It is exactly what I wanted to perform. Thanks!

2016-03-10 13:02 GMT+01:00 Matthew Clarke <ma...@gmail.com>:

> If I am understanding correctly, you want to take a FlowFile coming from
> one processor and produce multiple copies. Each copy is then sent to
> different follow-on processors. Correct? This can be accomplished by simply
> connecting the success relationship multiple times from the single source
> processor to the multiple destination processors. NiFi will automatically
> clone the FlowFile when multiple relationships of the same type are
> connected. What is even better here is that NiFi does not duplicate the
> content but rather just adds additional pointers to the same content for
> each replicated FlowFile.
> On Mar 10, 2016 4:24 AM, "Pierre Villard" <pi...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have a use case where I need to "broadcast" a flow file to multiple
> > processors. At the moment, the only way I see to do that is to combine a
> > DuplicateFlowFile processor with a DistributeLoad processor. It seems to
> > work fine, but I am wondering if it would be more user friendly to have a
> > dedicated processor for this kind of operation? If you think so, I'll be
> > happy to have it done.
> >
> > Pierre
> >
>

Re: Broadcasting Flow File

[Matthew Clarke <ma...@gmail.com>]

If I am understanding correctly, you want to take a FlowFile coming from
one processor and produce multiple copies. Each copy is then sent to
different follow-on processors. Correct? This can be accomplished by simply
connecting the success relationship multiple times from the single source
processor to the multiple destination processors. NiFi will automatically
clone the FlowFile when multiple relationships of the same type are
connected. What is even better here is that NiFi does not duplicate the
content but rather just adds additional pointers to the same content for
each replicated FlowFile.
On Mar 10, 2016 4:24 AM, "Pierre Villard" <pi...@gmail.com>
wrote:

> Hi,
>
> I have a use case where I need to "broadcast" a flow file to multiple
> processors. At the moment, the only way I see to do that is to combine a
> DuplicateFlowFile processor with a DistributeLoad processor. It seems to
> work fine, but I am wondering if it would be more user friendly to have a
> dedicated processor for this kind of operation? If you think so, I'll be
> happy to have it done.
>
> Pierre
>