apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Farkas <...@datatorrent.com>
Subject Re: Running CassandraOutputOperator with newer library
Date Fri, 18 Dec 2015 13:43:16 GMT
Hi Priyanka,

I haven't seen this issue yet, but I am not using the newest version of
cassandra driver. This is the version I am using:


I did run into an issue where I was getting strange cassandra exceptions,
so I set the protocol to version 2.0 in the CassandraStore class like this
and the issue was resolved:

      cluster = Cluster.builder()


If you are still experiencing missing method issues due to different guava
versions it may be necessary to shade the version of guava used by apex.
Shading changes the package names of all the packages in a library by
appending a prefix, so that
all the classes in the guava version used by apex would look like this:
org.apache.apex.com.google.guavapackage.GuavaClass. This prevents version
clashes, and this technique is used by Flink for that reason. Perhaps we
can start that discussion again in a separate thread.

A temporary workaround could be to exclude guava from the apex dependencies
in your pom, that way the newest version of guava will be used.


On Fri, Dec 18, 2015 at 4:33 AM, Priyanka Gugale <priyag@apache.org> wrote:

> Hi,
> I am facing classpath issues when I try to use newer version (e.g. 2.1.x or
> 3.0.x) of cassandra library for CassandraOutputOperator.
> From datastax documents looks like we need to include few more libraries to
> setup java environment. (reference:
> http://docs.datastax.com/en/developer/java-driver/2.1/java-driver/reference/settingUpJavaProgEnv_r.html
> ).
> When I included the required libraries my ClassNotFound issue was resolved
> but then I was getting some methods missing error.
> Looks like, apex platform also uses guava library and it's version is lower
> than 14.0.1, I couldn't find the source though (Note: I was just trying to
> run unit tests here, not an application).
> Has anyone faced such issue earlier?
> -Priyanka

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message