I haven't had to deal with this problem specifically and don't know if there is a storm specific solution, but the general Java way of dealing with projects who have conflicting dependencies would be to either exclude one of the conflicting dependencies using maven and see if it works, otherwise rename the conflicting dependency using http://maven.apache.org/plugins/maven-dependency-plugin/usage.html so both projects can use there own versions of guava without the package names conflicting (and the jvm will load the correct classes for each dep).
On 25 October 2014 06:13, Gary Zhao <garyz...@gmail.com> wrote: > Hello > > Anyone encountered the following issue and any workaround? Our Storm > topology was written in Clojure. > > ---------------------------------------- > Our team is upgrading one of our storm topology from using cassandra 1.2 > to cassandra 2.0, and we have found one problem that is difficult to > tackle. Cassandra 2.0Java driver requires google guava 1.6. Unfortuanately, > storm 0.9.2 provides a lower version. Because of that, a topology will not > be able to contact Cassandra databases. > > Thanks > Gary > -- Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr <http://twitter.com/instaclustr> | +61 415 936 359
