You can use something like the maven shade plugin to use both of the libthrift jars.
I´ve avoided the issue by disabling assertions (-da). Any suggestions
on a better strategy?
On Thu, Aug 9, 2012 at 5:29 PM, Jose Flexa <email@example.com> wrote:
> I am triggering the assertion at the start of
> ColumnFamilyStore.getRangeSlice when setting a SlicePredicate with
> sliceRange.setStart(new byte), sliceRange.setFinish(new byte);
> sliceRange.setCount(Integer.MAX_VALUE); in a AWS EMR job flow. AWS EMR
> uses libthrift 0.7.0 but my cassandra cluster uses libthrift 0.6.0
> (cassandra 1.0.8).