cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13086) CAS resultset sometimes does not contain value column even though wasApplied is false
Date Mon, 09 Jan 2017 09:58:58 GMT


Alex Petrov commented on CASSANDRA-13086:

bq. Wouldn't it be better if Cassandra would return a null value instead of not including
the column?

We still need to make a distinction between: non existing partition / existing partition,
existing partition / null value, existing partition / no row. You can follow the tests I referred
to for more information on when the certain output is returned. 

> CAS resultset sometimes does not contain value column even though wasApplied is false
> -------------------------------------------------------------------------------------
>                 Key: CASSANDRA-13086
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Christian Spriegel
>            Priority: Minor
> Every now and then I see a ResultSet for one of my CAS queries that contain wasApplied=false,
but does not contain my value column.
> I just now found another occurrence, which causes the following exception in the driver:
> {code}
> ...
> Caused by: com.mycompany.MyDataaccessException: checkLock(ResultSet[ exhausted: true,
>     at com.mycompany.MyDAO._checkLock(
>     at com.mycompany.MyDAO._releaseLock(
>     ... 16 more
> Caused by: java.lang.IllegalArgumentException: value is not a column defined in this
>     at com.datastax.driver.core.ColumnDefinitions.getAllIdx(
>     at com.datastax.driver.core.ColumnDefinitions.getFirstIdx(
>     at com.datastax.driver.core.ArrayBackedRow.getIndexOf(
>     at com.datastax.driver.core.AbstractGettableData.getBytes(
>     at com.mycompany.MyDAO._checkLock(
>     ... 17 more
> {code}
> The query the application was doing:
> delete from "Lock" where lockname=:lockname and id=:id if value=:value;
> I did some debugging recently and was able to track these ResultSets to StorageProxy.cas()
to the "CAS precondition does not match current values {}" return statement.
> I saw this happening with Cassandra 3.0.10 and earlier versions.

This message was sent by Atlassian JIRA

View raw message