Thank you very much Aldrin. I will do this. -Jim On Wed, Mar 29, 2017 at 4:23 PM, Aldrin Piri <[email protected]> wrote:
> Hi Jim, > > lib_community is not one of the default directories NiFi searches. > > You can update nifi.properties to include additional paths via properties > such as those outlined in the System Administrator's guide in Core > Properties for nifi.nar.library.directory [1]. The description of this > follows: > > > The location of the nar library. The default value is ./lib and probably > should be left as is. > > NOTE: Additional library directories can be specified by using the > nifi.nar.library.directory. prefix with unique suffixes and separate paths > as values. > > For example, to provide two additional library locations, a user could > also specify additional properties with keys of: > > nifi.nar.library.directory.lib1=/nars/lib1 > nifi.nar.library.directory.lib2=/nars/lib2 > > Providing three total locations, including nifi.nar.library.directory. > > [1] https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html# > core-properties-br > > On Wed, Mar 29, 2017 at 4:12 PM, James McMahon <[email protected]> > wrote: > >> I am getting indications that my Python scripts being called by my >> InvokeScriptedProcessor processors are not finding callbacks nor PySet. I >> believe those may be in nars in lib_community. I don't see any explicit >> inclusion of lib_community in nifi.properties nor in bootstrap.conf. How >> does NiFi know to include lib_community in the libs it uses to find classes? >> >> Thnak you. - Jim >> > >
