What is best practice for auto deploying Apache Nifi custom .nar Files

[#1]

We have the need to create a custom nifi processor. The processor is working when deployed manually on a single node nifi server.

What is best practice to autodeploy the .nar file to all Nifi-Servers on a cluster and restart them?

Or can we place the nifi file somewhere central (e.g. HDFS) and configure Nifi to load the .nar file from there on startup? This would be HBase Coprocessor style like.. Is there possibly a way to do this via Ambari?

[#2 · Accepted solution]

Currently you just copy the NAR to the lib directory of every server and restart NiFi, you could script this process.

The NiFi community has talked about a future enhancement to have an extension registry where custom NARs could be uploaded, and then a given NiFi instance/cluster could load NARs from the registry. There is still a lot of design to be done, but this could potentially help with this scenario.

[#3]

After that any implementation for auto deploying Apache nifi .nar files?

[#4]

@shreyanshu_pare  You can now autoload nars by placing them in the ./extensions dir in the NiFi home.

https://www.nifi.rocks/auto-loading-extensions/