Processor Extensibility

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Processor Extensibility

Eric Secules
Hello,

I was wondering if there was a recommendation on how to extend the functionality of nifi processors without forking the nifi repository. I'm looking for a way to include a processor's nar in my project and extend from it. I'd also like to be able to extend that processor's test suite so I can leverage that. The "solution" I found (if you can call it that) was to copy the code from Validate record.java into a new class and make the changes I wanted to. 

Thanks,
Eric
Reply | Threaded
Open this post in threaded view
|

Re: Processor Extensibility

Matt Burgess-2
This is probably better suited for the dev list (not sure if you're
subscribed but please do, BCC'ing users and moving to dev), but the
implementations (components and their NARs) are not designed to be
subclassed for custom extensions outside the codebase, can you
describe your use case (and custom processor)? If there's a common
reusable interface we can talk about moving it to an API NAR and such,
but I believe in general the guidance is to do the copy/paste if you
need code from the existing components in the codebase.

Regards,
Matt

On Tue, Jul 7, 2020 at 10:14 PM Eric Secules <[hidden email]> wrote:
>
> Hello,
>
> I was wondering if there was a recommendation on how to extend the functionality of nifi processors without forking the nifi repository. I'm looking for a way to include a processor's nar in my project and extend from it. I'd also like to be able to extend that processor's test suite so I can leverage that. The "solution" I found (if you can call it that) was to copy the code from Validate record.java into a new class and make the changes I wanted to.
>
> Thanks,
> Eric