Apache NiFi Tutorial - Complete Guide (Part 18) - Working with Funnel in NiFi | #ApacheNiFi

preview_player
Показать описание
=============================
Apache NiFi Tutorial - Complete Guide (Part 18) - Working with Funnel in NiFi
=============================
How to apply and understand Apache NiFi is the best to use, powerful, and reliable system to process and distribute data. In this video series, you Learn with me (Manoj) how to use Apache NiFi easily. This Free Guide will show you exactly how to manipulate Apache NiFi to all the maximum capabilities. Some of the high-level capabilities and objectives of Apache NiFi include a Web-based user interface, Highly configurable, Data Provenance, Designed for an extension, and well secure.

Disclaimer - These above links are affiliate links

Follow me on other social media platforms to get regular updates.

#ApacheNiFi #NifiTutorial #LearnNifi
Рекомендации по теме
Комментарии
Автор

Thanks a lot for all the sessions on Nifi.Very useful for all the beginners.Please upload more sessions on Nifi

giridhar
Автор

Sir please make a video how to applying different type of join operation in the flow file record

binayakprasad
Автор

i love this presentation, could u please give more explanation regarding creation of custom processor and NAR file.

sansanjusingh
Автор

I tried to connect two GenerateFlowFile processors to a single PutFile processor without a Funnel. I connected them directly and it worked fine. It also works if I connect them using a funnel. So when exactly should we use a funnel? Could you please explain.

dharshinishanmuganathan
Автор

I'm missing the point, why to use a funnel. I understand that you can't connect output to input ports. But (at 3:00) why not just connect the two GenerateFlowFile-Outputs directly to the Log-Attribute? You don't need a funnel for that.
I think there are three purposes for using a funnel:
a) for changes: if you funnel MANY connections to one destination-processor, and you want to exchange the destination-processor, than you only have to draw one new connection - and not all the connections from all the source processors. (Same if you funnel one source to many destinations - then you can easy exchange the source-processor, because it has only one connection to the funnel).
b) prioritize queues: if you connect many processors to a funnel an then connect the funnel (for the combines queue) to one destination-processor, you can define prioritize-settings for the combined queue. (I think this is the most importent reason for funnels.)
c) possibly for controlling backpressure: by having the single queues and separate a combined queue, this has impact of the backpressure behaviour.

Marcel-
Автор

hello sir, Thats a great collection i regret to not get it before, could you please suggest of how to read parquet file in nifi. i am using fetch parquet but getting block every now and then

danishshadab
Автор

awesome explanation specially the ports, funnel, template and registry part.

niteshratnaparkhe