Hi Robert, It sounds like your NAR is including nifi-aws-processors, and so is the regular AWS NAR. Previously it wasn't obvious this was happening, and when NiFi started up it was finding those processors in one of the NARs and skipping the other one. With component versioning it is now more specific as to where the processors are coming from.
The preferred solution here would be to create a utility project like"nifi-aws-utils" underneath nifi-nar-bundles/nifi-extension-utils: https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-extension-utils This project would then contain the abstract processor, then your custom processors and the regular AWS processors could both depend on and include this JAR. If you wanted to submit a PR/patch that created this utility project, we'd be happy to help get it reviewed/merged, although I realize you would have to be dependent on the latest code in master until a release occurred with the change. Hope that helps. Thanks, Bryan On Thu, May 18, 2017 at 2:58 AM, Robert <[email protected]> wrote: > For my custom processor I am extending AbstractS3Processor. For that I use > nifi-aws-processors as a dependency. > With upgrade to 1.2.0, Nifi now loads also all aws processors that are > packed in nar as a depencency. Is there any way to avoid duplicated > processors that get loaded in that way? > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Duplicated-processors-when-using-nifi-processors-dependency-tp15902.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
