nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Thomsen <>
Subject Re: Questions re: customizing a NiFi processor
Date Thu, 14 Dec 2017 16:51:43 GMT

I'd recommend just forking NiFi and updating it with a patch. Writing your
own processor for this sounds like massive overkill for what you need. If
you know how to use Git, you'll be fine. You can add me on GitHub as a
reviewer when you're done (I can at least do the initial pass for Andy or
someone else).

The easiest way to do the compliance check when you think you're done is to
have another terminal open to $NIFI_ROOT and run this:

mvn clean install -Pcontrib-check -pl :some-module-name

Note that ":" at the start. It's required for Maven to identify it as a
module name. That'll build only the module you want to test.

You can also run just your own tests with:

mvn test -Dtest=org.apache.nifi.x.y.z.MyTest

Sometimes that's necessary if other tests are broken for whatever reason
and they're not related to your code.

On Sat, Dec 2, 2017 at 6:43 PM, James McMahon <> wrote:

> Good evening. I am familiar with NiFi and have developed a number of
> workflows using out -of-the-box processors. I now need to develop a custom
> version of PublishAMQP that permits the use of attributes in expression
> language to set specs for the AMQP target.
> I am not very familiar with Maven, but have done some initial research and
> hope I can bootstrap my effort following this link:
> custom-nifi-processor.html
> Lacking any experience developing custom processors, I'd like to understand
> how I would establish in my maven project the source code for the existing
> PublishAMQP. I'd like to modify that proven code base to allow the use of
> expression language to set other configuration properties.
> Can anyone help me with an example where source code for an existing
> processor is brought in from a github resource or the like to use as my
> starting point?
> Thank you in advance for any assistance. -Jim

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message