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 of these illegal re
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 and I am frequently
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 te
"value" in that message is the name of a column that is expect to be in
your table schema - the message is simply complaining that you have no
column named "value" in that table.
The error concerns the table schema, not any actual data in either the
statement or the table.
"metadata" is simply ref
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 was
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 contain
> any value
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