cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6801) INSERT with IF NOT EXISTS fails when row is an expired ttl
Date Thu, 06 Mar 2014 11:02:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922308#comment-13922308
] 

Sam Tunnicliffe commented on CASSANDRA-6801:
--------------------------------------------

I was able to reproduce this on a single node using the schema detailed above (but with SimpleStategy).
Flush is also unnecessary, the problem manifests without it. The additional commit added for
CASSANDRA-6623 (5ef53e6f7) fixes this.

> INSERT with IF NOT EXISTS fails when row is an expired ttl
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-6801
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6801
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Adam Hattrell
>
> I ran this on a 2 DC cluster with 3 nodes each.  
> CREATE KEYSPACE test WITH replication = {
> 'class': 'NetworkTopologyStrategy',
> 'DC1': '3',
> 'DC2': '3'
> };
> CREATE TABLE clusterlock (
> name text,
> hostname text,
> lockid text,
> PRIMARY KEY (name)
> ) ;
> Then add some data and flush it to ensure the sstables exist (didn't reproduce in memtables
for some reason).
> Then
>  insert into clusterlock (name, lockid, hostname) values  ( 'adam', 'tt', '111') IF NOT
EXISTS USING TTL 5;
> Wait for ttl to be reached then try again:
>  insert into clusterlock (name, lockid, hostname) values  ( 'adam', 'tt', '111') IF NOT
EXISTS USING TTL 5;
>  
> [applied]
> -----------
>      False
> select * shows no rows in table.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message