[CASSANDRA-8430] Updating a row that has a TTL produce unexpected results

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Not A Problem
• Fix Version/s: 2.0.11, 2.1.2, 2.2.0 beta 1
• Labels: cassandra ttl
• Severity: Normal
• Assignee: Unassigned
• Reporter: Alan Boudreault
• Tester: Alan Boudreault
• Created: 05/Dec/14 16:57
• Updated: 16/Apr/19 09:31
• Resolved: 08/Dec/14 08:19

Description

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:

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)