Re: CAS operation does not return value on failure

Update: It was actually the driver update (from 2.1.9 to 3.0.1) that solved the issue. I reverted by C* Server back to 2.2 and my test is still ok. On Mon, May 9, 2016 at 1:28 PM, horschi wrote: > I just retried with Cassandra 3.0.5 and it performs much better. Not a > single

Re: CAS operation does not return value on failure

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 wrote: > Hi, > > I am doing some testing on CAS operations

Re: CAS operation does not return value on failure

Hi Jack, sorry to keep you busy :-) There definitely is a column named "value" in the table. And most of the time this codepath works fine, even when my CAS update fails. But in very rare cases I get a ResultSet that contains applied=false but does not contain any value column. I just ran my

Re: CAS operation does not return value on failure

Hi Jack, I thought that it is Cassandra that fills the value on CAS failures. So the question if it is to be expected to have wasApplied()==false and not have any value in the ResultSet should belong here. So my question for this mailing list would be: Is it correct behaviour that C* returns

Re: CAS operation does not return value on failure

Probably better to ask this on the Java driver user list. -- Jack Krupansky On Wed, May 4, 2016 at 11:46 AM, horschi 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