[CASSANDRA-7537] Updates and partition tombstones are not given the same timestamp in a CAS batch

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Not A Problem
• Component/s: Feature/Lightweight Transactions
• Labels: LWT
• Severity: Normal
• Assignee: Unassigned
• Reporter: Nicolas Favre-Felix
• Created: 11/Jul/14 18:08
• Updated: 25/Oct/19 13:11
• Resolved: 11/Nov/15 17:03

Description

Create a table with one partition and 2 CQL rows:

CREATE TABLE t1 (
    k text,
    c text,
    v text,
    PRIMARY KEY(k,c)
);

BEGIN BATCH
    INSERT INTO t1 (k,c,v) VALUES ('x','1','1');
    INSERT INTO t1 (k,c,v) VALUES ('x','2','2');
APPLY BATCH;

CAS-delete the full partition based on the expected value of a single column:

cqlsh:ks1> SELECT * FROM t1 WHERE k='x';

 k | c | v
---+---+---
 x | 1 | 1
 x | 2 | 2

(2 rows)

cqlsh:ks1> BEGIN BATCH
       ...     UPDATE t1 SET v = '0' WHERE k = 'x' AND c = '1' IF v = '1';
       ...     DELETE FROM t1 WHERE k = 'x';
       ... APPLY BATCH;

 [applied]
-----------
      True

cqlsh:ks1> SELECT * FROM t1 WHERE k='x';

 k | c | v
---+---+---
 x | 1 | 0

(1 rows)

sstable2json reports that the updated column has a timestamp 1 greater than the partition delete:

{"key": "78","metadata": {"deletionInfo": {"markedForDeleteAt":1405097039224999,"localDeletionTime":1405097039}},"columns": [["1:v","0",1405097039225000]]}

All mutations in a CAS batch should be applied with the same timestamp.