Apache Nifi - PutIgniteCache Processor Document not found

2016-08-19 Thread Deepak Kumar 
Hi,I am using Apache Nifi PutIgniteCache Processor. I am not able to get 
configuration document related to this processor in link 
https://nifi.apache.org/docs/nifi-docs/components/ . Can you please provide 
more information on PutIgniteCache Processor.
Thanks & Regards
Deepak

Re: PutS3Object Error

2016-08-19 Thread dgm 
I just finished testing with Java 1.8 + JCE Unlimited (w/ DH Keys < 1024 
disabled) + BC 1.5.   still works.

 

I’m not exactly sure why Java 1.7 didn’t work for this one processor.   But 
based on what James posted below, he said: “That suggests that your JRE's 
java.security provider does not support the clone method used by the AWS SDK.”

just following his recommendation to update the version of java and that  
seemed to do the trick.

 

Thanks, 

Dan M

 

From: Daniel Morris 
Date: Friday, August 19, 2016 at 9:42 AM
To: 
Subject: Re: PutS3Object Error

 

In my java 1.7 environment, we have the JCE unlimited and BouncyCastle 1.46.

 

When I added a Java 1.8 environment and ran NiFi there, I have not yet added 
JCE or BouncyCastle yet.  That’s my plan today, to add each one and do some 
testing after adding each of the components.

 

 

Thanks, 

Dan M

 

From: Joe Skora 
Reply-To: 
Date: Friday, August 19, 2016 at 9:34 AM
To: 
Subject: Re: PutS3Object Error

 

That's great, but I'm not sure why that would have fixed it.

Did you change anything when you switched to 1.8?

 

On Fri, Aug 19, 2016 at 9:16 AM, dgm  wrote:

So far, upgrading to Java 1.8 resolved the issue I was experiencing.

 

 

Thanks, 

Dan Morris

443-992-2848

 

From: James Wing 
Reply-To: 
Date: Thursday, August 18, 2016 at 12:58 PM


To: 
Subject: Re: PutS3Object Error

 

I think you got it, Joe, it does make sense now.  I had wondered about the 
Unlimited Strength policy, but for... MD5?  I couldn't get over that.  Now, I 
am a bit surprised more people haven't run into this.

Dan, I'm afraid I don't know anything about configuring the java.security 
providers.  Telling you to sabotage BouncyCastle doesn't sound like good 
advice, but I'm not sure how to configure a happy coexistence between 
BouncyCastle and the AWS SDK.

Thanks,

James

 

On Thu, Aug 18, 2016 at 7:54 AM, Joe Skora  wrote:

The JDK does not require MessageDigest implementations to implement Cloneable, 
but the AWS code seems to expect digests to be cloneable.  Looking at Bouncy 
Castle, it's BCMessageDigest does not support Cloneable.


I'm not familiar enough to offer specifics, but if you can change to a 
different message digest that could eliminate the problem.

 

On Thu, Aug 18, 2016 at 9:03 AM, dgm  wrote:

James, in addition to using the BC security provider, I was already using the 
latest JCE Unlimited Strength Jurisdiction Policy Files from Oracle.

 

Thanks, 

Dan Morris

443-992-2848

 

From: Daniel Morris 
Date: Thursday, August 18, 2016 at 7:23 AM
To: 
Subject: Re: PutS3Object Error

 

Thanks James.   So when you say the JRE security provider, are you referring to 
bouncycastle?   If so, I am currently using bcprov-jdk16-1.46.jar.

 

Thanks, 

Dan M

 

From: James Wing 
Reply-To: 
Date: Wednesday, August 17, 2016 at 11:45 PM


To: 
Subject: Re: PutS3Object Error

 

The IllegalStateException appears to be a response to a 
CloneNotSupportException thrown by java.security.MessageDigest.  That suggests 
that your JRE's java.security provider does not support the clone method used 
by the AWS SDK.  Is your java.security setup the JRE default?  Would it be 
possible to try a different, maybe newer, JRE?

And it's always a bonus when the code throwing your exception is foreshadowed 
with the ominous "should never occur":

private MessageDigest cloneFrom(MessageDigest from) {
try {
return (MessageDigest)from.clone();
} catch (CloneNotSupportedException e) { // should never occur
throw new IllegalStateException("unexpected", e);
}
}

(see 
https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/internal/MD5DigestCalculatingInputStream.java#L54)

Thanks,

James

 

On Wed, Aug 17, 2016 at 5:40 PM, dgm  wrote:

Sure thing!

 

Version: Nifi 0.7.0, RHEL 6.8, with Java JRE 1.7.0_101

 

Logs/Stacktrace:

 

2016-08-17 19:01:09,339 INFO [Timer-Driven Process Thread-3] 
o.a.n.p.attributes.UpdateAttribute UpdateAttribute[id=7b485633-a6e3-4aee-   
   a671-d5b6f2599040] Updated attributes for 
StandardFlowFileRecord[uuid=bda2e6c2-7a20-4354-a65f-3ed5b9ef4d06,claim=StandardContentClaim
   [resourceClaim=StandardResourceClaim[id=1471471716616-15, 
container=default, section=15], offset=44598, length=3467],offset=0,
  name=20160817190051056-low-text_json_good.json,size=3467]; transferring 
to 'success'

   29 2016-08-17 19:01:09,346 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.processors.aws.s3.PutS3Object PutS3Object[id=a0836995-c787-40b1-   
  a8bb-c6f39bb9f37a]

Re: PutS3Object Error

2016-08-19 Thread dgm 
In my java 1.7 environment, we have the JCE unlimited and BouncyCastle 1.46.

 

When I added a Java 1.8 environment and ran NiFi there, I have not yet added 
JCE or BouncyCastle yet.  That’s my plan today, to add each one and do some 
testing after adding each of the components.

 

 

Thanks, 

Dan M

 

From: Joe Skora 
Reply-To: 
Date: Friday, August 19, 2016 at 9:34 AM
To: 
Subject: Re: PutS3Object Error

 

That's great, but I'm not sure why that would have fixed it.

Did you change anything when you switched to 1.8?

 

On Fri, Aug 19, 2016 at 9:16 AM, dgm  wrote:

So far, upgrading to Java 1.8 resolved the issue I was experiencing.

 

 

Thanks, 

Dan Morris

443-992-2848

 

From: James Wing 
Reply-To: 
Date: Thursday, August 18, 2016 at 12:58 PM


To: 
Subject: Re: PutS3Object Error

 

I think you got it, Joe, it does make sense now.  I had wondered about the 
Unlimited Strength policy, but for... MD5?  I couldn't get over that.  Now, I 
am a bit surprised more people haven't run into this.

Dan, I'm afraid I don't know anything about configuring the java.security 
providers.  Telling you to sabotage BouncyCastle doesn't sound like good 
advice, but I'm not sure how to configure a happy coexistence between 
BouncyCastle and the AWS SDK.

Thanks,

James

 

On Thu, Aug 18, 2016 at 7:54 AM, Joe Skora  wrote:

The JDK does not require MessageDigest implementations to implement Cloneable, 
but the AWS code seems to expect digests to be cloneable.  Looking at Bouncy 
Castle, it's BCMessageDigest does not support Cloneable.


I'm not familiar enough to offer specifics, but if you can change to a 
different message digest that could eliminate the problem.

 

On Thu, Aug 18, 2016 at 9:03 AM, dgm  wrote:

James, in addition to using the BC security provider, I was already using the 
latest JCE Unlimited Strength Jurisdiction Policy Files from Oracle.

 

Thanks, 

Dan Morris

443-992-2848

 

From: Daniel Morris 
Date: Thursday, August 18, 2016 at 7:23 AM
To: 
Subject: Re: PutS3Object Error

 

Thanks James.   So when you say the JRE security provider, are you referring to 
bouncycastle?   If so, I am currently using bcprov-jdk16-1.46.jar.

 

Thanks, 

Dan M

 

From: James Wing 
Reply-To: 
Date: Wednesday, August 17, 2016 at 11:45 PM


To: 
Subject: Re: PutS3Object Error

 

The IllegalStateException appears to be a response to a 
CloneNotSupportException thrown by java.security.MessageDigest.  That suggests 
that your JRE's java.security provider does not support the clone method used 
by the AWS SDK.  Is your java.security setup the JRE default?  Would it be 
possible to try a different, maybe newer, JRE?

And it's always a bonus when the code throwing your exception is foreshadowed 
with the ominous "should never occur":

private MessageDigest cloneFrom(MessageDigest from) {
try {
return (MessageDigest)from.clone();
} catch (CloneNotSupportedException e) { // should never occur
throw new IllegalStateException("unexpected", e);
}
}

(see 
https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/internal/MD5DigestCalculatingInputStream.java#L54)

Thanks,

James

 

On Wed, Aug 17, 2016 at 5:40 PM, dgm  wrote:

Sure thing!

 

Version: Nifi 0.7.0, RHEL 6.8, with Java JRE 1.7.0_101

 

Logs/Stacktrace:

 

2016-08-17 19:01:09,339 INFO [Timer-Driven Process Thread-3] 
o.a.n.p.attributes.UpdateAttribute UpdateAttribute[id=7b485633-a6e3-4aee-   
   a671-d5b6f2599040] Updated attributes for 
StandardFlowFileRecord[uuid=bda2e6c2-7a20-4354-a65f-3ed5b9ef4d06,claim=StandardContentClaim
   [resourceClaim=StandardResourceClaim[id=1471471716616-15, 
container=default, section=15], offset=44598, length=3467],offset=0,
  name=20160817190051056-low-text_json_good.json,size=3467]; transferring 
to 'success'

   29 2016-08-17 19:01:09,346 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.processors.aws.s3.PutS3Object PutS3Object[id=a0836995-c787-40b1-   
  a8bb-c6f39bb9f37a] PutS3Object[id=a0836995-c787-40b1-a8bb-c6f39bb9f37a] 
failed to process due to java.lang.IllegalStateException:   
unexpected; rolling back session: java.lang.IllegalStateException: unexpected

   30 2016-08-17 19:01:09,349 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.processors.aws.s3.PutS3Object

   31 java.lang.IllegalStateException: unexpected

   32 at 
com.amazonaws.services.s3.internal.MD5DigestCalculatingInputStream.cloneFrom(MD5DigestCalculatingInputStream.java:54)
 ~[na:na]

   33 at 
com.amazonaws.services.s3.internal.MD5DigestCalculatingInputStream.mark(MD5DigestCalculatingInputStream.java:66)

Re: PutS3Object Error

2016-08-19 Thread Joe Skora 
That's great, but I'm not sure why that would have fixed it.

Did you change anything when you switched to 1.8?

On Fri, Aug 19, 2016 at 9:16 AM, dgm  wrote:

> So far, upgrading to Java 1.8 resolved the issue I was experiencing.
>
>
>
>
>
> Thanks,
>
> Dan Morris
>
> 443-992-2848
>
>
>
> *From: *James Wing 
> *Reply-To: *
> *Date: *Thursday, August 18, 2016 at 12:58 PM
>
> *To: *
> *Subject: *Re: PutS3Object Error
>
>
>
> I think you got it, Joe, it does make sense now.  I had wondered about the
> Unlimited Strength policy, but for... MD5?  I couldn't get over that.  Now,
> I am a bit surprised more people haven't run into this.
>
> Dan, I'm afraid I don't know anything about configuring the java.security
> providers.  Telling you to sabotage BouncyCastle doesn't sound like good
> advice, but I'm not sure how to configure a happy coexistence between
> BouncyCastle and the AWS SDK.
>
> Thanks,
>
> James
>
>
>
> On Thu, Aug 18, 2016 at 7:54 AM, Joe Skora  wrote:
>
> The JDK does not require MessageDigest
> 
> implementations to implement Cloneable, but the AWS code
> 
> seems to expect digests to be cloneable.  Looking at Bouncy Castle, it's
> BCMessageDigest
> 
> does not support Cloneable.
>
>
> I'm not familiar enough to offer specifics, but if you can change to a
> different message digest that could eliminate the problem.
>
>
>
> On Thu, Aug 18, 2016 at 9:03 AM, dgm  wrote:
>
> James, in addition to using the BC security provider, I was already using
> the latest JCE Unlimited Strength Jurisdiction Policy Files from Oracle.
>
>
>
> Thanks,
>
> Dan Morris
>
> 443-992-2848
>
>
>
> *From: *Daniel Morris 
> *Date: *Thursday, August 18, 2016 at 7:23 AM
> *To: *
> *Subject: *Re: PutS3Object Error
>
>
>
> Thanks James.   So when you say the JRE security provider, are you
> referring to bouncycastle?   If so, I am currently using
> bcprov-jdk16-1.46.jar.
>
>
>
> Thanks,
>
> Dan M
>
>
>
> *From: *James Wing 
> *Reply-To: *
> *Date: *Wednesday, August 17, 2016 at 11:45 PM
>
>
> *To: *
> *Subject: *Re: PutS3Object Error
>
>
>
> The IllegalStateException appears to be a response to a
> CloneNotSupportException thrown by java.security.MessageDigest.  That
> suggests that your JRE's java.security provider does not support the clone
> method used by the AWS SDK.  Is your java.security setup the JRE default?
> Would it be possible to try a different, maybe newer, JRE?
>
> And it's always a bonus when the code throwing your exception is
> foreshadowed with the ominous "should never occur":
>
> private MessageDigest cloneFrom(MessageDigest from) {
> try {
> return (MessageDigest)from.clone();
> } catch (CloneNotSupportedException e) { // should never occur
> throw new IllegalStateException("unexpected", e);
> }
> }
>
> (see https://github.com/aws/aws-sdk-java/blob/master/aws-java-
> sdk-s3/src/main/java/com/amazonaws/services/s3/internal/
> MD5DigestCalculatingInputStream.java#L54)
>
> Thanks,
>
> James
>
>
>
> On Wed, Aug 17, 2016 at 5:40 PM, dgm  wrote:
>
> Sure thing!
>
>
>
> Version: Nifi 0.7.0, RHEL 6.8, with Java JRE 1.7.0_101
>
>
>
> Logs/Stacktrace:
>
>
>
> 2016-08-17 19:01:09,339 INFO [Timer-Driven Process Thread-3]
> o.a.n.p.attributes.UpdateAttribute UpdateAttribute[id=7b485633-a6e3-4aee-
> a671-d5b6f2599040] Updated attributes for StandardFlowFileRecord[uuid=
> bda2e6c2-7a20-4354-a65f-3ed5b9ef4d06,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1471471716616-15,
> container=default, section=15], offset=44598, length=3467],offset=0,
> name=20160817190051056-low-text_json_good.json,size=3467]; transferring
> to 'success'
>
>29 2016-08-17 19:01:09,346 ERROR [Timer-Driven Process Thread-3]
> o.a.nifi.processors.aws.s3.PutS3Object PutS3Object[id=a0836995-c787-40b1-
> a8bb-c6f39bb9f37a] PutS3Object[id=a0836995-c787-40b1-a8bb-c6f39bb9f37a]
> failed to process due to java.lang.IllegalStateException:
> unexpected; rolling back session: java.lang.IllegalStateException:
> unexpected
>
>30 2016-08-17 19:01:09,349 ERROR [Timer-Driven Process Thread-3]
> o.a.nifi.processors.aws.s3.PutS3Object
>
>31 java.lang.IllegalStateException: unexpected
>
>32 at com.amazonaws.services.s3.internal.
> MD5DigestCalculatingInputStream.cloneFrom(MD5DigestCalculatingInputStream.java:54)
> ~[na:na]
>
>33 at

Re: adding dependencies like jdbc drivers to the build

2016-08-19 Thread Joe Witt 
Captured the elements of this thread
https://issues.apache.org/jira/browse/NIFI-2604  Please alter/update
as needed.

On Fri, Aug 19, 2016 at 5:51 AM, Peter Wicks (pwicks)  wrote:
> While you are at it… can you make it so it supports more than one file in
> that field, probably comma delimited?  I have one JDBC driver that for
> whatever reason requires two separate JAR’s.
>
>
>
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Friday, August 19, 2016 5:30 AM
> To: users@nifi.apache.org
> Subject: RE: adding dependencies like jdbc drivers to the build
>
>
>
> Adding jars to the lib directory is not ideal as it pollutes all
> classloaders.  We should add expression language support to the path
> property if it isn't already as that makes variable registry access
> available which makes use of the same template or flow in different
> environments easier.
>
>
>
> On Aug 19, 2016 7:27 AM, "Peter Wicks (pwicks)"  wrote:
>
> Sumanth,
>
>
>
> If the driver is in your lib directory already then you should leave the
> path empty.  All jar’s in your lib directory are loaded in the classpath for
> all NAR’s.
>
>
>
> Personally I have three different JDBC drivers in my lib directory to make
> them available for whoever needs them (MS SQL, SAP Hana, Teradata, and will
> add Oracle soon).
>
>
>
> --Peter
>
>
>
> From: Sumanth Chinthagunta [mailto:xmlk...@gmail.com]
> Sent: Thursday, August 18, 2016 8:56 PM
> To: users@nifi.apache.org
> Subject: Re: adding dependencies like jdbc drivers to the build
>
>
>
> It would be nice if we support relative paths for driver jar. E.g.,
> ./lib/mariadb-java-client-1.1.7.jar
>
> This let flow templet portable (dev -> prod)
>
>
>
>
>
> Sent from my iPhone
>
>
> On Aug 18, 2016, at 2:25 PM, Bryan Bende  wrote:
>
> For JDBC, if you are talking about the DBConnectionPool, you should be able
> to reference a driver as an external file such as
> file:///var/tmp/mariadb-java-client-1.1.7.jar'
>
>
>
> If you are talking about something different besides the DBConnectionPool
> then it depends what processor/component...
>
> If you look in the lib directory you will see all the NAR files, each NAR
> has one or more components along with all of the other JARs it needs, and
> each NAR has isolated class loading so that they will not interfere with
> each other.
>
>
>
> You would need to figure out which NAR you are dealing with and add a
> dependency to one of the poms related to that NAR.
>
>
>
> -Bryan
>
>
>
>
>
> On Thu, Aug 18, 2016 at 4:33 PM, Tom Gullo  wrote:
>
> If I want to add a jdbc driver or any third party dependency where should I
> add that dependency in the Maven build for Nifi?
>
>
>
> Thanks
>
> -Tom
>
>
>
>

Re: PutS3Object Error

2016-08-19 Thread dgm 
So far, upgrading to Java 1.8 resolved the issue I was experiencing.

 

 

Thanks, 

Dan Morris

443-992-2848

 

From: James Wing 
Reply-To: 
Date: Thursday, August 18, 2016 at 12:58 PM
To: 
Subject: Re: PutS3Object Error

 

I think you got it, Joe, it does make sense now.  I had wondered about the 
Unlimited Strength policy, but for... MD5?  I couldn't get over that.  Now, I 
am a bit surprised more people haven't run into this.

Dan, I'm afraid I don't know anything about configuring the java.security 
providers.  Telling you to sabotage BouncyCastle doesn't sound like good 
advice, but I'm not sure how to configure a happy coexistence between 
BouncyCastle and the AWS SDK.

Thanks,

James

 

On Thu, Aug 18, 2016 at 7:54 AM, Joe Skora  wrote:

The JDK does not require MessageDigest implementations to implement Cloneable, 
but the AWS code seems to expect digests to be cloneable.  Looking at Bouncy 
Castle, it's BCMessageDigest does not support Cloneable.


I'm not familiar enough to offer specifics, but if you can change to a 
different message digest that could eliminate the problem.

 

On Thu, Aug 18, 2016 at 9:03 AM, dgm  wrote:

James, in addition to using the BC security provider, I was already using the 
latest JCE Unlimited Strength Jurisdiction Policy Files from Oracle.

 

Thanks, 

Dan Morris

443-992-2848

 

From: Daniel Morris 
Date: Thursday, August 18, 2016 at 7:23 AM
To: 
Subject: Re: PutS3Object Error

 

Thanks James.   So when you say the JRE security provider, are you referring to 
bouncycastle?   If so, I am currently using bcprov-jdk16-1.46.jar.

 

Thanks, 

Dan M

 

From: James Wing 
Reply-To: 
Date: Wednesday, August 17, 2016 at 11:45 PM


To: 
Subject: Re: PutS3Object Error

 

The IllegalStateException appears to be a response to a 
CloneNotSupportException thrown by java.security.MessageDigest.  That suggests 
that your JRE's java.security provider does not support the clone method used 
by the AWS SDK.  Is your java.security setup the JRE default?  Would it be 
possible to try a different, maybe newer, JRE?

And it's always a bonus when the code throwing your exception is foreshadowed 
with the ominous "should never occur":

private MessageDigest cloneFrom(MessageDigest from) {
try {
return (MessageDigest)from.clone();
} catch (CloneNotSupportedException e) { // should never occur
throw new IllegalStateException("unexpected", e);
}
}

(see 
https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/internal/MD5DigestCalculatingInputStream.java#L54)

Thanks,

James

 

On Wed, Aug 17, 2016 at 5:40 PM, dgm  wrote:

Sure thing!

 

Version: Nifi 0.7.0, RHEL 6.8, with Java JRE 1.7.0_101

 

Logs/Stacktrace:

 

2016-08-17 19:01:09,339 INFO [Timer-Driven Process Thread-3] 
o.a.n.p.attributes.UpdateAttribute UpdateAttribute[id=7b485633-a6e3-4aee-   
   a671-d5b6f2599040] Updated attributes for 
StandardFlowFileRecord[uuid=bda2e6c2-7a20-4354-a65f-3ed5b9ef4d06,claim=StandardContentClaim
   [resourceClaim=StandardResourceClaim[id=1471471716616-15, 
container=default, section=15], offset=44598, length=3467],offset=0,
  name=20160817190051056-low-text_json_good.json,size=3467]; transferring 
to 'success'

   29 2016-08-17 19:01:09,346 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.processors.aws.s3.PutS3Object PutS3Object[id=a0836995-c787-40b1-   
  a8bb-c6f39bb9f37a] PutS3Object[id=a0836995-c787-40b1-a8bb-c6f39bb9f37a] 
failed to process due to java.lang.IllegalStateException:   
unexpected; rolling back session: java.lang.IllegalStateException: unexpected

   30 2016-08-17 19:01:09,349 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.processors.aws.s3.PutS3Object

   31 java.lang.IllegalStateException: unexpected

   32 at 
com.amazonaws.services.s3.internal.MD5DigestCalculatingInputStream.cloneFrom(MD5DigestCalculatingInputStream.java:54)
 ~[na:na]

   33 at 
com.amazonaws.services.s3.internal.MD5DigestCalculatingInputStream.mark(MD5DigestCalculatingInputStream.java:66)
 ~[na:na]

   34 at 
com.amazonaws.internal.SdkFilterInputStream.mark(SdkFilterInputStream.java:96) 
~[na:na]

   35 at 
com.amazonaws.internal.SdkFilterInputStream.mark(SdkFilterInputStream.java:96) 
~[na:na]

   36 at 
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:472) 
~[na:na]

   37 at 
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:317) ~[na:na]

   38 at 
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595) 
~[na:na]

   39 at 
com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1382) 
~[na:na]

   40 at

RE: adding dependencies like jdbc drivers to the build

2016-08-19 Thread Peter Wicks (pwicks) 
While you are at it… can you make it so it supports more than one file in that 
field, probably comma delimited?  I have one JDBC driver that for whatever 
reason requires two separate JAR’s.

From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Friday, August 19, 2016 5:30 AM
To: users@nifi.apache.org
Subject: RE: adding dependencies like jdbc drivers to the build


Adding jars to the lib directory is not ideal as it pollutes all classloaders.  
We should add expression language support to the path property if it isn't 
already as that makes variable registry access available which makes use of the 
same template or flow in different environments easier.

On Aug 19, 2016 7:27 AM, "Peter Wicks (pwicks)" 
> wrote:
Sumanth,

If the driver is in your lib directory already then you should leave the path 
empty.  All jar’s in your lib directory are loaded in the classpath for all 
NAR’s.

Personally I have three different JDBC drivers in my lib directory to make them 
available for whoever needs them (MS SQL, SAP Hana, Teradata, and will add 
Oracle soon).

--Peter

From: Sumanth Chinthagunta [mailto:xmlk...@gmail.com]
Sent: Thursday, August 18, 2016 8:56 PM
To: users@nifi.apache.org
Subject: Re: adding dependencies like jdbc drivers to the build

It would be nice if we support relative paths for driver jar. E.g., 
./lib/mariadb-java-client-1.1.7.jar
This let flow templet portable (dev -> prod)



Sent from my iPhone

On Aug 18, 2016, at 2:25 PM, Bryan Bende 
> wrote:
For JDBC, if you are talking about the DBConnectionPool, you should be able to 
reference a driver as an external file such as 
file:///var/tmp/mariadb-java-client-1.1.7.jar'

If you are talking about something different besides the DBConnectionPool then 
it depends what processor/component...
If you look in the lib directory you will see all the NAR files, each NAR has 
one or more components along with all of the other JARs it needs, and each NAR 
has isolated class loading so that they will not interfere with each other.

You would need to figure out which NAR you are dealing with and add a 
dependency to one of the poms related to that NAR.

-Bryan


On Thu, Aug 18, 2016 at 4:33 PM, Tom Gullo 
> wrote:
If I want to add a jdbc driver or any third party dependency where should I add 
that dependency in the Maven build for Nifi?

Thanks
-Tom

RE: adding dependencies like jdbc drivers to the build

2016-08-19 Thread Joe Witt 
Adding jars to the lib directory is not ideal as it pollutes all
classloaders.  We should add expression language support to the path
property if it isn't already as that makes variable registry access
available which makes use of the same template or flow in different
environments easier.

On Aug 19, 2016 7:27 AM, "Peter Wicks (pwicks)"  wrote:

Sumanth,



If the driver is in your lib directory already then you should leave the
path empty.  All jar’s in your lib directory are loaded in the classpath
for all NAR’s.



Personally I have three different JDBC drivers in my lib directory to make
them available for whoever needs them (MS SQL, SAP Hana, Teradata, and will
add Oracle soon).



--Peter



*From:* Sumanth Chinthagunta [mailto:xmlk...@gmail.com]
*Sent:* Thursday, August 18, 2016 8:56 PM
*To:* users@nifi.apache.org
*Subject:* Re: adding dependencies like jdbc drivers to the build



It would be nice if we support relative paths for driver jar. E.g.,
./lib/mariadb-java-client-1.1.7.jar

This let flow templet portable (dev -> prod)





Sent from my iPhone


On Aug 18, 2016, at 2:25 PM, Bryan Bende  wrote:

For JDBC, if you are talking about the DBConnectionPool, you should be able
to reference a driver as an external file such as file:///var/tmp/mariadb-
java-client-1.1.7.jar'



If you are talking about something different besides the DBConnectionPool
then it depends what processor/component...

If you look in the lib directory you will see all the NAR files, each NAR
has one or more components along with all of the other JARs it needs, and
each NAR has isolated class loading so that they will not interfere with
each other.



You would need to figure out which NAR you are dealing with and add a
dependency to one of the poms related to that NAR.



-Bryan





On Thu, Aug 18, 2016 at 4:33 PM, Tom Gullo  wrote:

If I want to add a jdbc driver or any third party dependency where should I
add that dependency in the Maven build for Nifi?



Thanks

-Tom