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]] Sent: Tuesday, November 10, 2015 11:45 AM To: [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. ________________________________
