No, it appears that an entry is now in nifi.properties that does indeed
tell NiFi to also look in lib_community. It looks like tis (in 0.7.x):
nifi.nar.library.directory.community=./lib_community
And so I can only presume it is looking in that lib directory as well as in
nifi.nar.library.director
Jim,
You said your Python modules might be in NARs? If so I'm not sure
InvokeScriptedProcessor can pick them up. Normally Python modules are installed
or otherwise located in a directory, and you add that directory to the Module
Directory property of InvokeScriptedProcessor, and it will do a sy
Thank you very much Aldrin. I will do this. -Jim
On Wed, Mar 29, 2017 at 4:23 PM, Aldrin Piri 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 Syst
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:
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 kno
Hi James,
Thank you for the swift reply!
NiFi is acting as a super-user that will interact with AWS to grab some
files, do some transformations, and put them elsewhere. While we can
create a role for NiFi to access all necessary S3 buckets and other AWS
services, we need to make sure it is a sec
Adam,
Would you please share a bit more about why the various roles and how many
you would have? I'm curious how it's working in practice, we don't always
get feedback when stuff isn't broken :).
You are correct that the current AWSCredentialsProviderControllerService
assumes a single, unvaried
I've got a use case where files from S3 will need to fetched/put by
dynamically assuming a role. I see that
the AWSCredentialsProviderControllerService supports setting an assumed
role, however it is a fixed value. I'm not too familiar with the
controller service API -- Would it be possible/diff
For the record,
The way we figured out to fix this is to create a new XML file for each
root level container that we use (tentatively fs.xml). This fs.xml looks
like the following:
fs.defaultFS
wasb://contai...@accountname.blob.core.windows.net/
We then include the core-sit
*Matt, I am adapting a model I found in a reply at Hortonworks for using
Python from InvokeScriptedProcessor:*
*from org.apache.nifi.processor import Processor, Relationship*
*from org.python.core import PySet*
*class PythonProcessor(Processor):*
* def __init__(self):*
* self.REL_S
10 matches
Mail list logo