nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Payne <>
Subject Re: Custom processors and restart
Date Fri, 04 May 2018 20:16:51 GMT

Dynamically deploying extensions is very much on the roadmap. There is actually a Feature
Proposal [1]
written that outlines some of the ideas about how it would work. The idea being that extensions
would be
published to an Extension Registry, and NiFi would then interact with that Extension Registry
(or registries)
to pull in the extensions at runtime as needed.



On May 4, 2018, at 4:01 PM, Guido De Caso <<>>

Hi everyone,

I've been reading about Apache NiFi and trying it out at my company as a data-pipeline-as-a-service

We are envisioning that third-parties, or at least different organizations within my company
should be able to write custom connectors.

As far as I've been reading around, including in previous posts on this e-mail group, the
current flow for doing so requires NiFi to be restarted. In other platforms that we are considering
(e.g., Spring Cloud Dataflow) this can be achieved without restarting the platform itself.

NiFi has been so far our preferred choice to go forward, but the must-restart-to-install-custom-processor
requirement is making it a hard sell internally.

Is "hot-load" something that the NiFi team sees in the roadmap? Or does NiFi architecture
make this fundamentally impossible to achieve?

Thanks in advance!

Guido de Caso
Software Architect  |  ❖ Medallia, Inc.

 [] <>
 [] <>
 [] <>
 [] <>

View raw message