ok we just figured out that we need another jar - kudu-client-tools.jar. that one bundled with a proper version async lib and slf4j-api.
slf4j-simple.jar has to be added separately but you do not have to do it if it is okay to suppress kudu client logs. kudu-client.jar and kudu-client-tools.jar are symlinked to a proper version of jars for CDH parcel. /opt/cloudera/parcels/CDH/lib/kudu/kudu-client.jar /opt/cloudera/parcels/CDH/lib/kudu/kudu-client-tools.jar /opt/cloudera/parcels/CDH/jars/slf4j-simple-1.7.5.jar On Wed, Jan 2, 2019 at 2:44 PM Boris Tyukin <[email protected]> wrote: > Hi guys, > > sorry for a dumb question but why kudu-client.jar does not include async > and slf4j-api and slf4j-simple libs? I need to call Kudu API from a simple > groovy script and had to add 3 other jars explicitly. > > I see these libs were excluded on purpose: > https://github.com/apache/kudu/blob/master/java/kudu-client/build.gradle > > Kafka client, for example, is a single jar. > > My challenge now which version of these libs to pick, how to support them > so they won't break in future etc. > > Even on CDH cluster, while kudu client is shipped with parcel, one has to > know exact versions of other 3 jars for client to work. > > Maybe I am missing something here and there is an easy way, especially on > CDH since it ships already with Kudu. > > Boris >
