Re: [EXT] New to Nifi - Failed to update database due to a failed batch update

Hi Aruna, The XML files in the Gist page are NiFi Templates. You can import those XML from NiFi UI. Please look at this documentation for detail: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Import_Template As to PutDatabase doing nothing, the '1' on the right top corner of

Re: ComponentLog and JUnit

I've done some more digging with mvn dependency:tree. It looks like a jar I'm importing in my pom includes logback-classic, version 1.0.9, at the compile scope. The exceptions I'm getting is likely due to it being an old version of logback-classic. Notably, the logback-classic in the jar I'm

Re: Using MiNiFi as a library from with a Java program

I understand your desire for a bundled SDK for data routing, but NiFi/MiNiFi isn’t designed for that right now. As the code is open source, you are welcome to extract pieces you find useful to build your own. Kafka Connect or some other libraries are probably more relevant to what you are

Re: Using MiNiFi as a library from with a Java program

Thanks for that detailed response Andy. I was not sure if it is advisable to use MiNiFi without connecting it back to NiFi, so good to get clarity on that. To take a stab at providing a reasoning for the 'MiNiFi as a library' use case: - I am looking to provide a library that exposes an SDK to

Re: ComponentLog and JUnit

*tl;dr:* When using TestRunner, I can only get logging to log to the console/standard out when logback-classic is present in the test-scope. Is it safe to say that NiFi, when using the TestRunner, requires logback-classic to be present in the test scope in the pom.xml? I've got my stuff

Re: Processing multiple lines per flowfile with ExtractGrok

Thanks Joe and Bryan. The setup is little more involved but I was able to get ConvertRecord running with a grok reader and a json writer. And I can confirm that setup splits records as expected by newline. Nice touch to have multiple records contained in the same flow file! Thanks for the tip and

Re: ComponentLog and JUnit

I think another option is to use the simple SLF4J logger org.slf4j slf4j-simple test Then you probably wouldn't need the logback.xml file since you wouldn't be logging through logback at that point. On Wed, Sep 27, 2017 at 10:40 AM, Ryan H wrote:

Re: ComponentLog and JUnit

I figured it out... I was missing the logback-test.xml file (now included) and in my pom.xml: I had: ch.qos.logback logback-*core* test Instead I swapped to: ch.qos.logback logback-*classic* test And the logs are outputting now. Ryan On Wed, Sep 27, 2017 at 10:20 AM,

Re: ComponentLog and JUnit

Hi Andy, It's a custom processor I'm writing. I was scratching my head wondering if that is it, or adding a test dependency for logback has something to do with it. I just copy/pasted this one:

Re: Nifi site-to-site: How does it work and how can it scale?

Thank you very much, Joe. Do we have any recommendation regarding the maximum throughput a single input port can achieve to understand when we need to upgrade to having multiple input ports? Will it be a bottleneck at all? Or before hitting that we probably already hit other bottlenecks? Is