[
https://issues.apache.org/jira/browse/CASSANDRA-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386306#comment-14386306
]
Aleksey Yeschenko commented on CASSANDRA-6363:
----------------------------------------------
Given that it's been a while without seeing any similar reports, and that the
bug was only visible in then unstable CAS implementation in 2.0.2, I say go
ahead and close.
> CAS not applied on rows containing an expired ttl column
> --------------------------------------------------------
>
> Key: CASSANDRA-6363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6363
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Linux/x64 2.0.2 4-node cluster
> Reporter: Michał Ziemski
> Assignee: Stefania
>
> CREATE TABLE session (
> id text,
> usr text,
> valid int,
> PRIMARY KEY (id)
> );
> insert into session (id, usr) values ('abc', 'abc');
> update session using ttl 1 set valid = 1 where id = 'abc';
> (wait 1 sec)
> And
> delete from session where id = 'DSYUCTCLSOEKVLAQWNWYLVQMEQGGXD' if usr
> ='demo';
> Yields:
> [applied] | usr
> -----------+-----
> False | abc
> Rather than applying the delete.
> Executing:
> update session set valid = null where id = 'abc';
> and again
> delete from session where id = 'DSYUCTCLSOEKVLAQWNWYLVQMEQGGXD' if usr
> ='demo';
> Positively deletes the row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
