Re: export from Teradata

Just to add to what Mark said, perhaps you can raise a JIRA (as new Feature) to add an optional property to the processor config where such property would point to an additional class path (to support your case and many others). We are doing it with few processors already. Cheers Oleg On Jul

Re: export from Teradata

Hi Dima, That will work, however it is very dangerous to put jar files into NiFi's lib/ directory. We generally recommend only putting NAR's into the lib/ directory, as any jar that is there will be inherited by all NARs and all classloaders. So you may end up getting some really funny results

Re: export from Teradata

Just in case someone has the same problem. Copying both teradata jars to nifi's lib directory and leaving the "jar url" blank solved the problem for us. I was able to start exporting data from Teradata. Best regards, Dima On Thu, Jul 14, 2016 at 4:34 PM, Anuj Handa wrote:

Re: export from Teradata

Hi Dima, You will have to create an über jar from the JDBC drivers provided by Teradata and copy the uberjar into the lib folder of nifi. As Matt pointed out the instructions are in the email thread. You can refer them. Anuj > On Jul 14, 2016, at 9:35 AM, Matt Burgess

Re: export from Teradata

Dima, There was a discussion on how to get the SQL processors working with Teradata a little while ago: http://mail-archives.apache.org/mod_mbox/nifi-users/201605.mbox/%3CCAEXY4srXZkb2pMGiOFGs%3DrSc_mHCFx%2BvjW32RjPhz_K1pMr%2B%2Bg%40mail.gmail.com%3E Looks like it involves making a fat JAR to