nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <>
Subject Re: Duplicated processors when using nifi processors dependency
Date Sun, 21 May 2017 17:28:05 GMT
Currently the AWS NAR contains the processors, controller service API, and controller service
implementation, all in one NAR.

Typically the controller service API should be in its own NAR, so there should be something


The nifi-aws-service-api module would have the AWSCredentialsProviderService interface. The
nifi-aws-nar would have a NAR dependency on nifi-aws-service-api-nar.

Setting it up this way, you nifi-aws-utils project could have a provided dependency on the
nifi-aws-service-api, and then your custom NAR could have a NAR dependency on nifi-aws-service-api-nar.

There is some more information here about setting up controller services:
<> <>

> On May 20, 2017, at 10:06 AM, Robert <> wrote:
> I tired to do move abstract aws processors from
> nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors to newly created
> nifi-aws-utils.
> Problem that I face now is with AWSCredentialsProviderControllerService that
> imo should stay under nifi-aws-bundle, but it is required by
> AbstractAWSCredentialsProviderProcessor that should be moved to
> nifi-aws-utils as it is used by abstract aws processors.
> What is the preferred way to solve this?
> Should I created new 'nifi-aws-service-bundle' under nifi-nar-bundles and
> both nifi-aws-processors and nifi-aws-utils can depend on it?
> --
> View this message in context:
> Sent from the Apache NiFi Developer List mailing list archive at

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