Re: Processor classpath

No worries, while "it's working but I don't entirely know why" satisfies me immediately, it does keep niggling at the back of my mind (not least in case it randomly stops working!). Thanks for all the help, James On 7 July 2017 at 17:44, Bryan Bende wrote: > Actually after

Re: Processor classpath

Here's where strace tells me my processor is looking for core-site.xml: [nifi@nifi nifi-1.3.0]$ strace -p 22189 -f 2>&1 | grep core-site.xml [pid 22284] stat("/opt/nifi/nifi-1.3.0/conf/core-site.xml", [pid 22284]

Re: Processor classpath

Hi James, I'm saying that it should not find a core-site.xml in NiFi's conf directory because the conf directory is not on the classpath of processors. Are you saying you have tested putting it there and believe it is finding it? -Bryan On Fri, Jul 7, 2017 at 11:08 AM, James Srinivasan

Re: Processor classpath

Hi Bryan, That all makes sense...except this is my own NiFi processor, not one of the built-in Hadoop ones: https://github.com/jrs53/geomesa-nifi So I'm still confused as to why core-site.xml is picked up from NiFi's conf directory, but very happy that it is! On 5 July 2017 at 21:55, Bryan

Re: Processor classpath

James, Just to clarify... the conf directory of NiFi is not on the classpath of processors. The behavior with core-site.xml is because the Hadoop client used by NiFi provides this behavior, and not NiFi itself. Basically if you create a new Hadoop Configuration object and you don't provide it

Re: Processor classpath

Thanks, I ended up stracing the NiFi process to see where it was actually trying to load my config file from. Helpfully, the list of locations included the NiFi conf directory, which is just perfect for me. I don't want to keep the config file (core-site.xml for Hadoop) in my NAR itself since it

Re: Processor classpath

It's not a classpath, but rather a user configurable location, exposed as a processor property. Does it help? Andrew On Tue, Jul 4, 2017, 4:32 PM James Srinivasan wrote: > Hi, > > I'm developing a processor which needs to read some of its config from > the

Processor classpath

Hi, I'm developing a processor which needs to read some of its config from the classpath. Reading the docs etc., NiFi's classpath is a little funky - where's the best (least worst?) location for such files? I note that the HDFS processors can read their config (core-site.xml etc) from the