Re: Enrichment flow using ScriptedLookup

Hi folks, thanks for the explanations! I've opened a JIRA ticket describing this issues plus a few more that I faced since I started learning NiFi ( https://issues.apache.org/jira/browse/NIFI-4569). It got a little verbose so forgive-me and feel free to ignore it. ;) Most of my hit backs I

Re: Enrichment flow using ScriptedLookup

Eric, Because LookupService implements ControllerService, you must implement initialize(ControllerServiceInitializationContext context), which Andy's script provides an empty body for. However that context object has a method called getLogger() on it, so you can override the initialize() method

Re: Enrichment flow using ScriptedLookup

eric can you please file a JIRA to reflect the awkward process you had to go through so we can improve it. Thanks On Sun, Nov 5, 2017 at 9:37 AM, Eric Chaves wrote: > Ok, I managed to make to make it work. I had to add "log.dir=./logs" to > bootstrap.conf file in order to have

Re: Enrichment flow using ScriptedLookup

Ok, I managed to make to make it work. I had to add "log.dir=./logs" to bootstrap.conf file in order to have the logs generated. I got a little lost because this property is not mentioned at the docs but I could figured it out reading the logback.xml Once the logs began to be generated I could

Re: Enrichment flow using ScriptedLookup

They go to logs/nifi-app.log. I think is actually WARN by default. You'll need to tinker with the log levels (it's not straight enable/disable) to get that working. On Sun, Nov 5, 2017 at 8:54 AM, Eric Chaves wrote: > Hi Mike, I'm running nifi using the official docker image

Re: Enrichment flow using ScriptedLookup

Hi Mike, I'm running nifi using the official docker image (version 1.4.0) and my logs folder is empty. I was looking at bootstrap.conf, logback.xml and nifi.properties but couldn't found any config value that may disable/enable log. Where should those logs be going? 2017-11-04 12:55 GMT-02:00

Re: Enrichment flow using ScriptedLookup

You may need to update the logback xml file in the conf folder. There is a line in there for the processor package. Might be too high for info. On Sat, Nov 4, 2017 at 10:50 AM Eric Chaves wrote: > Hi folks, > > I'm trying to adapt the flow described at >