In addition to what Matt said, I just wanted to mention that in the master branch, the base AWS classes have been separated into their own JAR to make them more reusable.
See nifi-aws-abstract-processors here: https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-aws-bundle After a release with this change, you might be able to add the nifi-aws-abstract-processors JAR (and all other transitive JARs) to the modules path of your InvokeScriptedProcessor to make it work. On Mon, Nov 20, 2017 at 1:11 PM, Matt Burgess <[email protected]> wrote: > The other NARs are not immediately available to the scripting NAR, and > in general you usually have to put your processor in the same NAR as > the base class, or put the base class and interfaces in to an API JAR > and share that somehow. IMO there's a little too much voodoo to try > and make it work with InvokeScriptedProcessor. You might be better off > creating a NAR bundle using the Maven archetype and coding your > processor in Groovy, bringing in the necessary dependencies (such as > setting your NAR parent to nifi-aws-nar) and all that. Let us know if > you run into trouble setting any of that up, will gladly help where I > can. > > Regards, > Matt > > [1] > https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions#MavenProjectsforExtensions-MavenProcessorArchetype > > On Mon, Nov 20, 2017 at 12:58 PM, Eric Chaves <[email protected]> wrote: >> Hi folks, >> >> I'm writing some groovy scripts for that will use the AWS-SDK. My first shot >> was to write a InvokeScriptedProcessor that extends the >> AbstractAWSCredentialsProviderProcessor but the script is unable to resolve >> this class. >> >> Is it possible to reference a class in a NAR bundle? >> >> Regards, >> >> Eric
