nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <>
Subject [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Registry
Date Wed, 08 Feb 2017 21:50:24 GMT
NiFi Community,

I'd like to initiate a discussion around creating a sub-project of
NiFi to encompass the registry capabilities outlined in several of the
feature proposals on the Wiki [1]. A possible name for this
sub-project is simply "NiFi Registry".

Currently there are two feature proposals that call for NiFi to
interact with an external registry:

Configuration Management of Flows [2]  - This feature proposal calls
for a flow registry where versioned flows can be published and
consumed, allowing flows to be easily migrated between environments .

Extension Registry [3] - This feature proposal calls for a place to
publish NARs containing extensions, allowing NiFi to decouple itself
from including all of the NARs in the main distribution, and allowing
better discovery of available extensions.

The idea would be to create a NiFi Registry sub-project, with
sub-modules for the various registries. These registries could then be
packaged and distributed as a single artifact and run as a
complimentary application to NiFi and MiNiFi. NiFi would not require
the registry application, however, a given NiFi could be configured to
know about one or more flow registries, or one or more extension

Creating a sub-project would allow the registry code to evolve
independently of NiFi and be released on it's own timeline. In
addition, it would make tracking issues/work much clearer through a
separate JIRA.

Please discuss and provide and thoughts or feedback.




View raw message