You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alan Boudreault (JIRA)" <ji...@apache.org> on 2014/12/05 17:58:12 UTC

[jira] [Created] (CASSANDRA-8430) Updating a row that has a TTL produce unexpected results

Alan Boudreault created CASSANDRA-8430:
------------------------------------------

             Summary: Updating a row that has a TTL produce unexpected results
                 Key: CASSANDRA-8430
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8430
             Project: Cassandra
          Issue Type: Bug
            Reporter: Alan Boudreault
             Fix For: 3.0, 2.1.2, 2.0.11
         Attachments: test.sh

Reported on stackoverflow: http://stackoverflow.com/questions/27280407/cassandra-ttl-gets-set-to-0-on-primary-key-if-no-ttl-is-specified-on-an-update?newreg=19e8c6757c62474985fef7c3037e8c08

I can reproduce the issue with 2.0, 2.1 and trunk. I've attached a small script to reproduce the issue with CCM, and here is it's output:

{code}
aboudreault@kovarro:~/dev/cstar/so27280407$ ./test.sh 
Current cluster is now: local
Insert data with a 5 sec TTL
INSERT INTO ks.tbl (pk, foo, bar) values (1, 1, 'test') using TTL 5;

 pk | bar  | foo
----+------+-----
  1 | test |   1

(1 rows)

Update data with no TTL
UPDATE ks.tbl set bar='change' where pk=1;
sleep 6 sec
BUG: Row should be deleted now, but isn't. and foo column has been deleted???

 pk | bar    | foo
----+--------+------
  1 | change | null

(1 rows)

Insert data with a 5 sec TTL
INSERT INTO ks.tbl (pk, foo, bar) values (1, 1, 'test') using TTL 5;

 pk | bar  | foo
----+------+-----
  1 | test |   1

(1 rows)

Update data with a higher (10) TTL
UPDATE ks.tbl USING TTL 10 set bar='change' where pk=1;
sleep 6 sec
BUG: foo column has been deleted?

 pk | bar    | foo
----+--------+------
  1 | change | null

(1 rows)

sleep 5 sec
Data is deleted now after the second TTL set during the update. Is this a bug or the expected behavior?

(0 rows)
{code}






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)