Agreed. We will look into adding support for Hive in a much more straight-forward way. Of course, this isn't something that will happen in the next couple of hours or likely the next couple of days, so I was looking for a way to answer your earlier question of: "is there anything that we can do in the meantime?"
But seeing that this is becoming more than a classpath issue, it's not likely something that we will be able to address until then. Thanks -Mark > On Sep 23, 2015, at 2:33 PM, vthiru2006 <vthiru2...@gmail.com> wrote: > > I would definitely support Joe on this. It's been painful. We now created a > Uber jar which has all dependency jars and placed it in the classpath and it > still fails to load the driver jars. It throws back kerberos error that it > doesn't have a right keytab. Main thing is considering the fact that NIFI is > built to be a light weighted application, we shouldn't keep adding jars in > classpath lib. > > We need this DBCP component to support hive2 with kerberos principal and > keytab setup and make it work in a straight forward way. If it is > NoClassFound issues, then it is fine(we can create an uber jar and point > that lib path instead of having it in classpath lib). But when it is > something more than that, then there is no point in having tool do it or > having it as a component that supports hive. > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/NIFI-DBCP-connection-pool-not-working-for-hive-tp2863p2941.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
