I just retried with Cassandra 3.0.5 and it performs much better. Not a single of these illegal results.
I guess my recommendation for anyone using CAS is: Upgrade to >= 3.x :-) On Wed, May 4, 2016 at 5:46 PM, horschi <hors...@gmail.com> wrote: > Hi, > > I am doing some testing on CAS operations and I am frequently having the > issue that my resultset says wasApplied()==false, but it does not contain > any value. > > > This behaviour of course leads to the following Exception when I try to > read it: > > Caused by: java.lang.IllegalArgumentException: value is not a column > defined in this metadata > at > com.datastax.driver.core.ColumnDefinitions.getAllIdx(ColumnDefinitions.java:273) > at > com.datastax.driver.core.ColumnDefinitions.getFirstIdx(ColumnDefinitions.java:279) > at > com.datastax.driver.core.ArrayBackedRow.getIndexOf(ArrayBackedRow.java:68) > at > com.datastax.driver.core.AbstractGettableData.getBytes(AbstractGettableData.java:131) > > > > My questions now are: > > Is it to be expected that a failing CAS operation sometimes does this? > > if yes: Shouldn't there a possibility on the driver side to handle this in > a better was, e.g. add a "hasColumn()" method or something to the ResultSet? > > if no: Is that perhaps a symptom to a greater issue in cassandra? > > > kind regards, > Christian > > PS: I also appreciate general feedback on the entire C* CAS topic :-) > > >
