Thanks for the kind words Shalin. This is something that is in development as 
Bryan mentioned. It’s a great time to contribute ideas and suggestions, as well 
as get involved with contributing code if you’re interested. We always welcome 
input from the community, especially if you have a real world use case for this 
with specific requirements and scenarios. That will help us build something 
that doesn’t just check off features, but solves real problems. 


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Oct 14, 2019, at 2:24 PM, Shalin Mehta <shal.n.me...@gmail.com> wrote:
> 
> Hey Bryan,
> 
> Thanks for the information, especially the 1.10.0 dependency. I know that
> there's been a lot of motion toward that release in the last couple weeks,
> so I'll continue keeping an eye on that while looking into the
> functionality in NiFi Registry 0.5.0. If there are any further suggestions
> for reading about the planned evolution, I'd love to know, but I'm sure
> this will keep me busy for a while.
> 
> Thanks again,
> 
> Shalin
> 
> On Mon, Oct 14, 2019 at 4:33 PM Bryan Bende <bbe...@gmail.com> wrote:
> 
>> Hi Shalin,
>> 
>> There is a minimal version of an extension registry as part of NiFi
>> Registry 0.5.0. You can see an example of how to upload a NAR in the
>> user guide [1].
>> 
>> The issue is that in order to use those end-points, your NAR needs to
>> be built with NiFi 1.10.0 which hasn't been released yet. So we are
>> still in a little bit of a waiting period, but you could always build
>> NiFi master and set your NAR to use nifi-api 1.10.0-SNAPSHOT if you
>> wanted to try it out.
>> 
>> Thanks,
>> 
>> Bryan
>> 
>> [1]
>> https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
>> 
>> On Mon, Oct 14, 2019 at 4:22 PM Shalin Mehta <shal.n.me...@gmail.com>
>> wrote:
>>> 
>>> Hey all,
>>> 
>>> I'm starting to cut my teeth on the extensibility of NiFi through Custom
>>> Processors, and one of the big things on my mind is being able to manage
>> a
>>> catalog of them across an organization.
>>> 
>>> While watching the "BYOP" presentation given by Andy at DataWorks Summit
>>> Barcelona earlier this year (awesome presentation, by the way!), there
>> was
>>> a really quick note of a future Extension Registry within NiFi Registry.
>> I
>>> dug around a bit and only came up with this Confluence page outlining
>> ideas
>>> for such a thing:
>>> 
>>> 
>> https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions
>>> 
>>> Is there any more information out there around this effort, such as
>> updated
>>> notes or specific Jira(s) about it? I'd love to get a better sense of
>> what
>>> the community has in mind, and what the state of the addition is like
>> these
>>> days. Rolling my own incarnation through process and supporting tools is
>>> where my head is currently sitting, but something more "permanent" and in
>>> line with the direction of the Project is way more appealing.
>>> 
>>> Thanks much in advance,
>>> 
>>> Shalin
>> 

Reply via email to