Oleg, Replication simply means to make a copy of something. You're thinking of replication as distributed data replication in order to provide high availability, I believe. What we are talking about here is simply sending a FlowFile from Processor A to Processor B and also sending that same FlowFile (or a copy of it) from Processor A to Processor C.
So when you create two connections with the same relationship, you are sending a copy of the FlowFile to both connections (i.e., you are replicating it). Thanks -Mark > On Nov 11, 2015, at 7:42 AM, Oleg Zhurakousky <[email protected]> > wrote: > > I am still a bit confused with the problem that is being solved here. > “replication” implies some type of redundancy allowing processing that failed > “here” to be resumed “there”. > > What I am reading here is more about "content based routing” - (route to > their respective workflows based on their attribute) > > Am I missing something? > > Cheers > Oleg >> On Nov 10, 2015, at 5:35 PM, Andrew Grande <[email protected] >> <mailto:[email protected]>> wrote: >> >> As mentioned, simply keep connecting things together (e.g. multiple >> 'success' relationship links). For better organization, consider putting a >> Funnel in the flow and connecting to it instead of a processor. >> >> Andrew >> >> From: Chakrader Dewaragatla <[email protected] >> <mailto:[email protected]>> >> Reply-To: "[email protected] <mailto:[email protected]>" >> <[email protected] <mailto:[email protected]>> >> Date: Tuesday, November 10, 2015 at 3:01 PM >> To: "[email protected] <mailto:[email protected]>" >> <[email protected] <mailto:[email protected]>> >> Subject: RE: Replicate flow files to multiple processors >> >> Thanks Mark. This should help. >> >> Our use case is to route traffic (flowflies) to multiple independent >> processors that inline route to their respective workflows based on their >> attribute. >> >> From: Mark Payne [[email protected] <mailto:[email protected]>] >> Sent: Tuesday, November 10, 2015 11:45 AM >> To: [email protected] <mailto:[email protected]> >> Subject: Re: Replicate flow files to multiple processors >> >> Chakri, >> >> This can be done with any Processor. You can simply drag multiple >> connections that have the same Relationship. >> >> For example, you can create a GetSFTP processor and draw a connection from >> GetSFTP to UpdateAttribute with the 'success' relationship. >> and then also draw a connection from GetSFTP to PutHDFS with the 'success' >> relationship. >> >> This will result in each FlowFile that is routed to 'success' going to both >> Processors. >> >> NiFi does this without copying the data or anything, simply by creating a >> new FlowFile that points to the same content on disk, so >> it is able to do this extremely efficiently. >> >> Thanks >> -Mark >> >> >> >> >>> On Nov 10, 2015, at 2:39 PM, Chakrader Dewaragatla >>> <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi - Do we have any built in processor that replicate flow files to >>> multiple processors in parallel (in memory, not staging on disk)? >>> I was looking at distributedload processor that distribute load on >>> weighted, roudrobin technique. I am looking for something that replicate >>> the flow files. >>> >>> Thanks, >>> -Chakri >>> The information contained in this transmission may contain privileged and >>> confidential information. It is intended only for the use of the person(s) >>> named above. If you are not the intended recipient, you are hereby notified >>> that any review, dissemination, distribution or duplication of this >>> communication is strictly prohibited. If you are not the intended >>> recipient, please contact the sender by reply email and destroy all copies >>> of the original message. >> >> The information contained in this transmission may contain privileged and >> confidential information. It is intended only for the use of the person(s) >> named above. If you are not the intended recipient, you are hereby notified >> that any review, dissemination, distribution or duplication of this >> communication is strictly prohibited. If you are not the intended recipient, >> please contact the sender by reply email and destroy all copies of the >> original message. >
